Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Crela

REMOTE · CRELA.IO · 2 COMPONENTS

Search the Crela software marketplace and publish, update and review your software from your agent.

−1 this week 77 Trust /100

Last scanned (14 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Recent critical change

Authorization (13 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3851 tokens (~240/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 70% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • “set_metadata” reworded the description of “age_rating_questionnaire” cosmetic
    • “set_metadata” reworded the description of “age_rating” cosmetic

    2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 18 Nov 26 −1
    • Tool “set_metadata” rewrote its description, which is the text the model reads security
    • Schema quality: 195 → 237 ▼ functional
    • New tool “get_product_page” functional
    • New tool “set_cover” functional
    • New tool “set_product_page” functional
  • 17 Nov 26 0
    • “set_metadata” reworded the description of “security_updates_until” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 16 Nov 26 0
    • “set_metadata” reworded the description of “price_eur” cosmetic
    • “set_metadata” reworded the description of “sale_price_eur” cosmetic

    2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 15 Nov 26 0
    • “set_metadata” reworded the description of “license” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 13 Nov 26 −10
    • Authorization: partial → fail ▼ critical
    • New tool “delete_software”, which the server declares destructive security
    • New tool “delete_media”, which the server declares destructive security
    • Tool coverage: 86% → 72% ▼ functional
    • Schema quality: pass → fail ▼ functional
    • Schema quality: excellent → good functional
    • Destructive annotations: pass → 100 functional
    • Server version: 1.0.0 → 2.0.0 functional
    • New tool “get_my_software_details” functional
    • New tool “get_review_report” functional
    • New tool “get_sdk_marker” functional
    • New tool “get_submission_requirements” functional
    • New tool “list_my_software” functional
    • New tool “preview_marker” functional
    • New tool “set_metadata” functional
    • New tool “update_media” functional
    • New tool “check_review_status” functional
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://crela.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=crela.io CN=YE1,O=Let's Encrypt,C=US 10 Nov 2026 8 Feb 2027 ECDSA 256 ECDSA-SHA384 66c097b068f6a6acb96b3070ebd106d3f05
SANs: crela.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of crela.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
crela.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://*.supabase.co https://media.crela.io; font-src 'self' data:; media-src 'self' https://media.crela.io; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com https://crela-software.4b6126c17a96c5fd90f646c65d3f9a53.r2.cloudflarestorage.com; frame-src 'none'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'; worker-src 'self' blob:; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://crela.io/mcp Verified 200
http (plaintext) http://crela.io/mcp HTTPS enforced 308 https://crela.io/mcp
MCP tools · 16 exposed · ~3,851 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_review_status ~189

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.

NameTypeReqDescription
software_idstringyes–

No output schema declared.

No examples provided.

delete_media ~114

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.

NameTypeReqDescription
media_idstringyesThe id of the media item (from get_my_software_details response)
software_idstringyes–

No output schema declared.

No examples provided.

delete_software ~87

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.

NameTypeReqDescription
software_idstringyes–

No output schema declared.

No examples provided.

get_my_software_details ~149

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.

NameTypeReqDescription
software_idstringyes–

No output schema declared.

No examples provided.

get_product_page ~172

Read the product page of one of your software items as set_product_page writes it: blocks (what visitors see), pending_blocks (your text changes waiting for review), media (every upload with id, type, size and where it appears), unplaced (screenshots in no block; they still show in the media stage at the top), hero (the clip at the top of the page), cover (the image on cards and launcher tiles), presentation (listing level with toward_ideal) and warnings (dead media ids, missing description block, no clip). Read it before set_product_page to get the media ids, and again afterwards to check that warnings is empty. Requires sign-in to your Crela account; your client asks you to connect when you first use it.

NameTypeReqDescription
software_idstringyes–

No output schema declared.

No examples provided.

get_review_report ~154

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.

NameTypeReqDescription
max_locations_per_findinginteger–How many locations to keep per finding, default 10
software_idstringyes–

No output schema declared.

No examples provided.

get_sdk_marker ~96

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.

NameTypeReqDescription
software_idstringyes–

No output schema declared.

No examples provided.

get_software ~61

Full public detail of one approved software item by its slug: description, price, platforms, version, system requirements and the url of its Crela page.

NameTypeReqDescription
slugstringyesThe software slug from search_software, e.g. "knowledge-editor"

No output schema declared.

No examples provided.

get_submission_requirements ~102

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_my_software ~125

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.

NameTypeReqDescription
limitinteger–Max rows, default 50
statusstring–Filter by review status

No output schema declared.

No examples provided.

preview_marker ~125

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.

NameTypeReqDescription
slugstringyesThe planned URL slug of the tool you are about to submit

No output schema declared.

No examples provided.

search_software ~171

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.

NameTypeReqDescription
categorystring––
langstring–Language of the software user interface, e.g. "de". Not the programming language.
limitinteger–Results per page, default 20
pageinteger–1-based page, see total_pages in the response
querystring–Full-text search over title and description
sortstring–Result ordering, default "latest"

No output schema declared.

No examples provided.

set_cover ~225

Choose one of your uploaded screenshots as the cover: the 16:9 image on website cards and launcher tiles. Without a chosen cover the first screenshot is used. Landscape, at least 1280 x 720 px. zoom (1 to 3) and focal_x/focal_y (0 to 1, the point that stays in view) set the crop; media_id null resets to the first screenshot. Get media ids from get_product_page. Requires sign-in to your Crela account; your client asks you to connect when you first use it.

NameTypeReqDescription
focal_xnumber–Horizontal point that stays in view, 0 (left) to 1 (right), default 0.5
focal_ynumber–Vertical point that stays in view, 0 (top) to 1 (bottom), default 0.5
media_id–yesId of an uploaded screenshot, or null to reset
software_idstringyes–
zoomnumber–Crop zoom, 1 (default) to 3

No output schema declared.

No examples provided.

set_metadata ~1,111

Change metadata (title, description, price, categories, tags, etc.) of an existing software - no binary upload. On an approved tool, a new title, description or long_description gets a quick automatic text check: it goes live at once, or the response has text_check with outcome "rejected" and a reason, and the current text stays. Changing categories or age_rating, or upgrading price_eur from 0 to a paid value, triggers a re-review; text changed in the same update waits for it. 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.

NameTypeReqDescription
age_rating––Every product needs an age rating before it is listed (Australian online safety codes; German JMStV for games). Send together with age_rating_source, age_rating_reasons and age_rating_questionnaire.…
age_rating_questionnaireobject–Every product: answer every content question truthfully (true = the software contains it). For games any true answer rules out age rating 0; for software that is not a game, contact and purchases are…
age_rating_reasons––Reasons for the age rating, e.g. "fantasy violence without blood"; required from 6
age_rating_sourcestring–Where the age rating comes from: self (your own assessment), usk, pegi or iarc
categoriesarray––
descriptionstring––
drm_modestring–Paid tools are forced to sdk_required server-side regardless of this
frameworkstring–Usually auto-detected from the build; override only if wrong
install_typestring–installer, portable, zip or script
licensestring–Leave it unset in almost all cases. An open source license (SPDX identifier) can only be set with the first submission; here only the unchanged value or an empty string (back to the Crela Standard EU…
long_descriptionstring––
max_devicesinteger–Max simultaneous devices per license (1-10)
network_hostsarray–Hosts your app connects to, e.g. ["api.example.com", "*.cdn.example.com"]. Every host that receives user or device data must also be named in privacy_policy (KO_09). Applies from the next build.
network_mode––Network allowlist mode: "none" = the app needs no network, "declared" = it only talks to the hosts in network_hosts, "user_chosen" = the user picks the servers. null clears it. Applies from the next…
platformsarray–Correct the platforms when the ZIP auto-detection got them wrong
price_eurnumber–0 for free, or at least €0.50 (the smallest amount our payment provider can charge)
privacy_policy––Privacy policy text; null clears it. KO_09 rejects a build whose code contacts an analytics or telemetry service that this text does not name.
safety_notes––Warnings and safety information buyers need, e.g. flashing lights or changes to system settings (plain text, max 2000 characters); null clears it
sale_ends_at––ISO timestamp when the sale ends; null = open-ended
sale_price_eur––Discounted price (at least €0.50 (the smallest amount our payment provider can charge) and below price_eur); null ends the sale. Buyers see the lowest price of the 30 days before the sale crossed out
security_updates_untilstring–Date until which you provide security updates (YYYY-MM-DD), not in the past; from 11 December 2027 at least two years from today; five years recommended. Shown to buyers before they buy. Can be chang…
software_idstringyes–
support_contact––Support contact shown to buyers, e.g. an email address; null clears it
system_requirementsstring––
tagsarray––
titlestring––
tool_languagesarray–ISO 639-1 codes of every language the software user interface is available in, e.g. ["en","de"]; replaces the whole list. NOT the programming language.
trial_daysinteger–Trial duration in days (1-90)
trial_enabledboolean–Enable a time-limited trial for a paid tool
unlistedboolean–true = take off market (hidden, not purchasable); false = re-list
video_url––https YouTube/Vimeo link; null removes the video entry

No output schema declared.

No examples provided.

set_product_page ~804

Replace the blocks of your product page; the page shows them top to bottom. Block types: {"type":"description"} shows your listing description (long_description) at that place, at most once; prefer it over copying the text. {"type":"text","html":"<h2>..</h2><p>..</p>"} free text (h2, h3, p, ul, ol, li, strong, em, a, blockquote). {"type":"mediaText","mediaId":id,"html":"<h3>..</h3><p>..</p>","imageSide":"left"|"right"} one screenshot next to a short text. {"type":"features","items":[{"title":"..","text":".."}]} a feature list: 1 to 6 points, title up to 80 and text up to 300 characters, plain text. {"type":"image","mediaIds":[ids],"view":..,"aspect":..,"fit":..} up to 12 screenshots; view plain, slides, carousel, laptop, iphone, android or tablet; aspect 16:9 (default), 16:10, 4:3, 1:1, 4:5 or 9:16 for plain, slides and carousel; fit cover (fills, may crop) or contain (whole image). {"type":"clip","mediaId":id,"view":..,"playback":"autoplay"|"click"} your preview clip, at most once; view plain, laptop, iphone, android or tablet; autoplay plays muted when it scrolls into view, click shows a play button. The clip always plays in the media stage at the top of the page; a clip block shows it again at its place. {"type":"video","youtubeId":"<id or YouTube URL>","view":..} a YouTube video, loaded only after a click. Media ids come from get_product_page; unknown ids are refused and nothing is saved. Every screenshot shows in the media stage at the top of the page, with or without a block. At most 40 blocks. On a software that is already on sale, changed text (text, mediaText and features blocks) gets a quick automatic text check: it goes live at once, or the response has text_check with outcome "rejected" and a reason, and the current page stays. If the check is unavailable, the text waits (the response has changes_pending_review) and is checked again automatically. Images, clip, video and layout go live at once. Read get_product_page afterwards: warnings should be empty.…

NameTypeReqDescription
blocksarrayyesThe whole page, top to bottom; replaces the current blocks. Schema in the tool description.
software_idstringyes–

No output schema declared.

No examples provided.

update_media ~166

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.

NameTypeReqDescription
media_idstringyesThe id of the media item (from get_my_software_details response)
software_idstringyes–
sort_orderinteger–Display position; lower values appear first
urlstring–New video URL (video entries only; https YouTube/Vimeo)

No output schema declared.

No examples provided.

Install

How do I install the Crela MCP server?

Crela is a hosted endpoint at https://crela.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · crela.io

# add to Claude Code
claude mcp add --transport http io-crela-mcp 'https://crela.io/mcp'
Common questions

What is the Crela MCP server?

Crela is an MCP server listed in the public MCP registry as io.crela/mcp. Search the Crela software marketplace and publish, update and review your software from your agent. This page covers its hosted endpoint (https://crela.io/mcp).

Is the Crela MCP server safe to use?

Crela scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Crela MCP server expose?

Crela exposes 16 tools: search_software, get_software, get_submission_requirements, list_my_software, get_my_software_details, and 11 more. Their descriptions and schemas cost roughly 3,851 tokens of context every time the server is loaded.

Does the Crela MCP server require authentication?

No. We connected to Crela without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Crela MCP server still maintained?

Crela is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Crela MCP server?

VerifyMCP ran 13 checks on Crela, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.