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.

Courio

REMOTE · API.COURIO.SI

Mail real paper letters (standard, registered, registered with receipt) worldwide. No account.

Available components

69 Trust /100

Last scanned (8 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Documents and Files

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 Security77
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 867 tokens (~216/item across 4 items; 4 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 Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 20% 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 4 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
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.

  • 5 Nov 26 0
    • Tool “get_coverage” rewrote its description, which is the text the model reads security
    • Tool “quote_letter” rewrote its description, which is the text the model reads security
    • Tool “send_letter” rewrote its description, which is the text the model reads security
  • 4 Nov 26 +2
    • DNSSEC: fail → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
  • 3 Nov 26 67

    First indexed and scored.

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 5 Nov 2026 · Probed https://api.courio.si/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=courio.si CN=YE2,O=Let's Encrypt,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA384 5e2551c2e653f4ab2520a4d71cae0db8688
SANs: *.courio.si, courio.si
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 secure

Validation of api.courio.si. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
si. present 42378 13 Verified
courio.si. present 2371 13 Verified
api.courio.si. Verified address RRset verified with the apex keys
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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.courio.si/mcp Verified 200
http (plaintext) http://api.courio.si/mcp HTTPS enforced 301 https://api.courio.si/mcp
MCP tools · 4 exposed · ~867 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
get_coverage ~181

Lists which destination countries and service levels Courio can mail a physical paper letter to, with an indicative "from" price (EUR including VAT, 1 black-and-white page), typical delivery time and the legal product name. No account or API key is needed. Call it before quote_letter to check a destination is served; pass a country (ISO 3166-1 alpha-2, e.g. "DE") to narrow the answer. Service levels: "standard" (ordinary mail, no proof), "tracked" (tracking only), "registered" (registered mail: proof of deposit), "registered_ar" (registered with acknowledgement of receipt: proof of delivery, the one to use for legal notices).

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 code, e.g. "DE"; omit for every country

No output schema declared.

No examples provided.

get_letter_status ~100

Returns the current status of a letter (awaiting_payment, paid, submitted, in_transit, delivered, failed, expired, ...), its timeline and, once available, proof links (proof of deposit for "registered", proof of delivery for "registered_ar"). No account is needed; the letter_id is the credential. Recipient details are partially redacted unless the request carries the API key that created the letter.

NameTypeReqDescription
letter_idstringyes–

No output schema declared.

No examples provided.

quote_letter ~282

Prices a physical letter (printed, enveloped and posted by Courio) and returns a quote_id. Free and commits to nothing: no account, no payment, nothing is mailed. Give the service level, sender and recipient postal addresses, and the document (pdf_base64, pdf_url, or plain/markdown text). The price is in EUR including VAT (set currency to "USD" to also see a USD price), fixed for 24 hours. The document is checked and content-moderated; a problem comes back as an error with a hint. Quotes are capped per day (limit_exceeded with retry_after): reuse a quote_id rather than re-quoting. Service levels: "standard" (ordinary mail, no proof), "tracked" (tracking only), "registered" (registered mail: proof of deposit), "registered_ar" (registered with acknowledgement of receipt: proof of delivery, the one to use for legal notices). The quote gives the estimated delivery time (estimated_delivery_days). Next step: show the price, the legal product and the terms of sale (terms_url) to the human, then call send_letter if they agree.

NameTypeReqDescription
currencystring––
document–yes–
optionsobject––
recipientobjectyes–
senderobjectyes–
servicestringyes–

No output schema declared.

No examples provided.

send_letter ~304

Creates the letter for a quote and returns a payment link (Stripe Checkout). No account is needed. YOU CANNOT PAY: show the price and the payment link to the human and ask them to open it and pay. The letter is mailed right after payment and cannot be cancelled or recalled once paid, so paying is the point of no return: make sure the human has seen the price, the recipient and the document first. Calling it again with the same quote_id returns the same letter and link (or its current status once it has been paid). The link expires after about 24 hours. Optionally pass webhook_url (public https) to be notified of status changes. Poll get_letter_status to follow the letter. Autonomous agents whose owner gave them a card through a Stripe Shared Payment Token (e.g. Link) can pay by card themselves with MPP through the REST API (POST /v1/letters with payment_method "mpp", which may be disabled: 422 payment_method_unavailable). Agents that can sign crypto payments can instead pay with x402 through the REST API (POST /v1/letters with payment_method "x402", which may be disabled on this deployment: 422 payment_method_unavailable); official x402 clients cap a payment at $1 by default, so raise the spend limit to cover the quoted price first.

NameTypeReqDescription
quote_idstringyes–
webhook_urlstring–Public https URL notified on each status change

No output schema declared.

No examples provided.

Install

How do I install the Courio MCP server?

Courio is a hosted endpoint at https://api.courio.si/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 · api.courio.si

# add to Claude Code
claude mcp add --transport http si-courio-courio 'https://api.courio.si/mcp'
Common questions

What is the Courio MCP server?

Courio is an MCP server listed in the public MCP registry as si.courio/courio. Mail real paper letters (standard, registered, registered with receipt) worldwide. No account. This page covers its hosted endpoint (https://api.courio.si/mcp).

Is the Courio MCP server safe to use?

Courio scores 69 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 Courio MCP server expose?

Courio exposes 4 tools: get_coverage, quote_letter, send_letter, get_letter_status. Their descriptions and schemas cost roughly 867 tokens of context every time the server is loaded.

Does the Courio MCP server require authentication?

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

Is the Courio MCP server still maintained?

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