Crela MCP server
io.crela/mcpcrela.iostreamable-httpv1.10.1Scanned
Search the Crela software marketplace and publish, update and review your software from your agent.
13 tools: 2 can delete or cancel things, 2 change things and 9 only read.
- Reads private data · 0
- Reads text others write · 5
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Crela MCP server can do
The Crela MCP server is published by crela.io, a domain the MCP Registry verified. It has 13 tools. It can delete or cancel things (2 tools: delete_software and delete_media) and create or change data (2 tools: set_metadata and update_media). 9 tools only read.
5 tools bring in text other people can write (search_software, get_software, list_my_software and 2 more); 1 tool can send data out of your system (update_media).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 1.10.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Deletes or cancels 2Claude Code: deny
delete_mediaPermanently delete a screenshot, logo or other media item from a software listing.No findings
Why it is in this group
- The name "delete_media" says "delete": a word for removing or ending something.
- The description says "Permanently delete".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Permanently delete a screenshot, logo or other media item from a software listing. Use get_my_software_details to get the media ids of uploaded files. Uploaded files (screenshots and logos) are also deleted from storage; video URL entries are only removed from the listing. Requires sign-in to your Crela account; your client asks you to connect when you first use it.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
delete_softwarePermanently and irreversibly delete one of your software items.No findings
Why it is in this group
- The name "delete_software" says "delete": a word for removing or ending something.
- The description says "irreversibly".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Permanently and irreversibly delete one of your software items. Only works if it has never been sold - sold tools cannot be deleted (buyers keep their claim); take those off the market with set_metadata { unlisted: true } instead. Requires sign-in to your Crela account; your client asks you to connect when you first use it.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
Changes things 2Claude Code: ask
set_metadataChange metadata (title, description, price, categories, tags, etc.) of an existing software - no binary upload.No findings
Why it is in this group
- The name "set_metadata" says "set": a word for a change.
Description, as the server wrote it Change metadata (title, description, price, categories, tags, etc.) of an existing software - no binary upload. Changing title, description, long_description or categories on an approved tool triggers a re-review. Upgrading price_eur from 0 to a paid value also triggers re-review. All other fields (tags, price reductions, tool_languages, unlisted) do NOT trigger re-review. Set unlisted:true to take an approved tool off the market (reversible with unlisted:false) - existing buyers keep access, it just cannot be newly purchased. Rate limit: 5 updates per tool per 24 h (shared with new builds). check_review_status shows your remaining budget. Requires sign-in to your Crela account; your client asks you to connect when you first use it.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
update_mediaUpdate a media item: the sort order of any item (lower sort_order appears first), or the URL of a video entry (https YouTube/Vimeo link only).Can send data outNo findings
Why it is in this group
- The name "update_media" says "update": a word for a change.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Update a media item: the sort order of any item (lower sort_order appears first), or the URL of a video entry (https YouTube/Vimeo link only). This tool does not create entries: a video is added with set_metadata { video_url }. Use get_my_software_details to get media ids. Provide at least one of sort_order/url. Requires sign-in to your Crela account; your client asks you to connect when you first use it.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
Only reads 9Show 9 read-only tools
check_review_statusPoll the lightweight review status of a submitted software (progress, sub-step, rate-limit budget).Reads text others writeNo findings
Why it is in this group
- The name "check_review_status" says "status": a word for reading.
What it can reach
- untrusted-inputThe name "check_review_status" says "status" and "review": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
Description, as the server wrote it Poll the lightweight review status of a submitted software (progress, sub-step, rate-limit budget). Returns { tool_id, tool_status, awaiting_media, missing_media, presentation, next_step, version, review_job_status, review_sub_step, review_passed, rejection_reason, review_started_at, review_completed_at, rate_limit }. awaiting_media true means the tool is approved but not listed yet because screenshots are missing (missing_media). Polling: poll every 30 s until review_job_status is neither "queued" nor "running"; a full review takes 5-15 minutes. If review_passed is false after completion: call get_review_report for structured findings. rate_limit.updates_remaining_today shows the budget shared by set_metadata and new builds. Requires sign-in to your Crela account; your client asks you to connect when you first use it.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_my_software_detailsRead the full metadata and media list of one of your own software items by software_id.No findings
Why it is in this group
- The name "get_my_software_details" says "get": a word for reading.
Description, as the server wrote it Read the full metadata and media list of one of your own software items by software_id. Works for all statuses (pending, approved, rejected). Returns { tool, media, missing_media, presentation } where media lists all uploaded screenshots/images with their ids and sizes, and presentation attests the listing level (incomplete, minimum, ideal) with toward_ideal, the steps left to the ideal presentation. Use this to verify current state after set_metadata, to get media ids before calling delete_media, or to read current metadata before an update. Requires sign-in to your Crela account; your client asks you to connect when you first use it.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_review_reportFetch the full review report of a submitted software: pass/fail, rejection reasons and structured findings to fix.Reads text others writeNo findings
Why it is in this group
- The name "get_review_report" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "get_review_report" says "get" and "review": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "fetch" and "review": it reads comments, which other people can write.
Description, as the server wrote it Fetch the full review report of a submitted software: pass/fail, rejection reasons and structured findings to fix. Heavier than check_review_status - call this only after the review has completed, not for live progress polling. Findings are capped at 10 locations each (a CVE finding can carry hundreds of near-identical ones); the response then sets truncated:true and locations_omitted per finding. Raise max_locations_per_finding when you actually need the long tail. Requires sign-in to your Crela account; your client asks you to connect when you first use it.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_sdk_markerFetch the per-tool SDK marker (KO-10) of an EXISTING tool by software_id.No findings
Why it is in this group
- The name "get_sdk_marker" says "get": a word for reading.
Description, as the server wrote it Fetch the per-tool SDK marker (KO-10) of an EXISTING tool by software_id. Embed it via the build env var CRELA_SDK_MARKER before building a new version. For a tool that does not exist yet use preview_marker (needs slug, not software_id). Requires sign-in to your Crela account; your client asks you to connect when you first use it.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_softwareFull public detail of one approved software item by its slug: description, price, platforms, version, system requirements and the url of its Crela page.Reads text others writeNo findings
Why it is in this group
- The name "get_software" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it Full public detail of one approved software item by its slug: description, price, platforms, version, system requirements and the url of its Crela page.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
get_submission_requirementsReturn the machine-readable submission rules for selling software on Crela (required fields, KO rules, bundle rules).No findings
Why it is in this group
- The name "get_submission_requirements" says "get": a word for reading.
Description, as the server wrote it Return the machine-readable submission rules for selling software on Crela (required fields, KO rules, bundle rules). Public, no sign-in required. Use it to check whether a project fits Crela before building. Uploading builds and screenshots needs files from disk and is only available in the local server (npx -y @crela/mcp). This server manages existing software: list_my_software, check_review_status, get_review_report, set_metadata.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
list_my_softwareList all software you own with its id, slug, review status (pending/approved/rejected/flagged), whether it is unlisted, price and sales count.Reads text others writeNo findings
Why it is in this group
- The name "list_my_software" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "review": it reads comments, which other people can write.
Description, as the server wrote it List all software you own with its id, slug, review status (pending/approved/rejected/flagged), whether it is unlisted, price and sales count. Use this to recover the software_id needed by check_review_status, set_metadata and delete_software. Unlike search_software, this also returns pending, rejected and unlisted tools. Requires sign-in to your Crela account; your client asks you to connect when you first use it.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
preview_markerCompute the per-tool SDK marker (KO-10) for a NOT-yet-created tool from its planned slug.No findings
Why it is in this group
- The name "preview_marker" says "preview": a word for reading.
Description, as the server wrote it Compute the per-tool SDK marker (KO-10) for a NOT-yet-created tool from its planned slug. Paid tools (price > 0) must embed this marker via the build env var CRELA_SDK_MARKER before building and submitting. For tools that already exist use get_sdk_marker (needs software_id, not slug). Returns { marker, slug, slug_available }. Requires sign-in to your Crela account; your client asks you to connect when you first use it.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
search_softwareSearch the Crela marketplace for reviewed software, apps and games you buy once and own - no subscription.Reads text others writeNo findings
Why it is in this group
- The name "search_software" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Search the Crela marketplace for reviewed software, apps and games you buy once and own - no subscription. Returns only approved, publicly listed tools, each with a url to its Crela page where it can be bought. Use limit (1-50) to keep the response small and page through the rest; get_software returns the full detail of one.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:55 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://crela.io/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://ifycgjwoqkweceamdvxq.supabase.co/auth/v1
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (2 destructive, 4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://crela.io/mcp: tools/list returned 16 tools to an anonymous client, including delete_software (destructive), delete_media (destructive), set_metadata (write), update_media (write), set_product_page (write) and 1 more
Posture changes
- Nov 20, 2026
- Tools that change things, listed without credentials: 0 to 6
- RFC 9728 protected resource metadata: none to https://crela.io/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://ifycgjwoqkweceamdvxq.supabase.co/auth/v1
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 6; RFC 9728 protected resource metadata: none -> https://crela.io/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://ifycgjwoqk…View diff
- Tools that change things, listed without credentials: 0 to 6
- RFC 9728 protected resource metadata: none to https://crela.io/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://ifycgjwoqkweceamdvxq.supabase.co/auth/v1
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Tools1 changed.~1 changedView diff
- Changed:set_metadataChanges thingsinputSchema
Tools1 changed.~1 changedView diff
- Changed:set_metadataChanges thingsinputSchema
Tools11 added.+11 addedView diff
- Added:check_review_statusOnly reads
- Added:delete_mediaDeletes or cancels
- Added:delete_softwareDeletes or cancels
- Added:get_my_software_detailsOnly reads
- Added:get_review_reportOnly reads
- Added:get_sdk_markerOnly reads
- Added:get_submission_requirementsOnly reads
- Added:list_my_softwareOnly reads
- Added:preview_markerOnly reads
- Added:set_metadataChanges things
- Added:update_mediaChanges things
Install
Pinned to version 1.10.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http crela https://crela.io/mcpclaude mcp add --transport http crela https://crela.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__crela__search_software",
"mcp__crela__get_software",
"mcp__crela__get_submission_requirements",
"mcp__crela__list_my_software",
"mcp__crela__get_my_software_details",
"mcp__crela__check_review_status",
"mcp__crela__get_review_report",
"mcp__crela__get_sdk_marker",
"mcp__crela__preview_marker"
],
"ask": [
"mcp__crela__set_metadata",
"mcp__crela__update_media"
],
"deny": [
"mcp__crela__delete_software",
"mcp__crela__delete_media"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as crela. Review it before you use it.
Capability tags behind 6 rules
- mcp__crela__search_software untrusted-input
- mcp__crela__get_software untrusted-input
- mcp__crela__list_my_software untrusted-input
- mcp__crela__check_review_status untrusted-input
- mcp__crela__get_review_report untrusted-input
- mcp__crela__update_media outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.crela/mcp/verify?hash=3da837a84dd0e25b7dba27b50d64f2503511f93b69cc0288db55cae8008cb612" | jq -e '.changed == false'Pinned hash 3da837a84dd0, from Nov 16, 2026, 15:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.crela/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.crela/mcp)Source: MCP Registry. Synced Nov 16, 2026, 17:17 UTC.
Crela MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Crela MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Crela MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: delete_software and delete_media.
Can the Crela MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Crela MCP server have?
- 13 tools: 2 destructive, 2 write, 9 read. delete_software, delete_media, set_metadata, update_media, search_software, get_software, get_submission_requirements, list_my_software and 5 more.
Does the Crela MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Crela MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): update_media.
Has the Crela MCP server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.