Courio (sendcourio.com)
REMOTE · API.SENDCOURIO.COM
Courio (sendcourio.com): mail real paper letters (standard, registered) worldwide. No account.
Available components
Last scanned (14 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Documents and Files
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1705 tokens (~341/item across 5 items; 5 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 Management0
- Stability check failed: schema churn in the 12 days we've observed: 0 tool removals, 5 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 69% 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 5 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
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 →
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.
- 16 Nov 26 +1
- A breaking change shipped without a version bump: still 1.0.1 ▼ security
- “send_feedback” added a required parameter “feedback”, so existing callers break ▼ functional
- “send_feedback” dropped the required parameter “capability” ▼ functional
- Tool coverage: 60% → 69% ▲ functional
- “send_letter” dropped the optional parameter “telemetry” cosmetic
- “quote_letter” dropped the optional parameter “telemetry” cosmetic
- “get_letter_status” dropped the optional parameter “telemetry” cosmetic
- “get_coverage” dropped the optional parameter “telemetry” cosmetic
- Tool “send_feedback” changed its title: Send feedback cosmetic
- 15 Nov 26 −3
- Stability: 0.17 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.1 ▼ security
- Schema quality: 198 → 348 ▼ functional
- “send_feedback” added a required parameter “context”, so existing callers break ▼ functional
- “get_coverage” added a required parameter “context”, so existing callers break ▼ functional
- “get_letter_status” added a required parameter “context”, so existing callers break ▼ functional
- “quote_letter” added a required parameter “context”, so existing callers break ▼ functional
- “send_letter” added a required parameter “context”, so existing callers break ▼ functional
- Tool coverage: 20% → 60% ▲ functional
- “get_coverage” added an optional parameter “conversation_id” cosmetic
- “get_coverage” added an optional parameter “llm_model” cosmetic
- “get_letter_status” added an optional parameter “conversation_id” cosmetic
- “get_letter_status” added an optional parameter “llm_model” cosmetic
- “quote_letter” added an optional parameter “conversation_id” cosmetic
- “quote_letter” added an optional parameter “llm_model” cosmetic
- “send_feedback” added an optional parameter “conversation_id” cosmetic
- “send_feedback” added an optional parameter “llm_model” cosmetic
- “send_letter” added an optional parameter “conversation_id” cosmetic
- “send_letter” added an optional parameter “llm_model” cosmetic
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 9 Nov 26 66
First indexed and scored.
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://api.sendcourio.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sendcourio.com | CN=YE2,O=Let's Encrypt,C=US | 9 Nov 2026 | 7 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 5fd2351026f1ec37c14ea92fde19e3c90d7 |
| SANs: *.sendcourio.com, sendcourio.com | ||||||
| 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 insecure
Validation of api.sendcourio.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| sendcourio.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.sendcourio.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.sendcourio.com/mcp | HTTPS enforced | 301 | https://api.sendcourio.com/mcp |
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 →
get_coverage Check coverage and indicative prices ~331
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).
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| conversation_id | string | – | The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics. |
| country | string | – | ISO 3166-1 alpha-2 code, e.g. "DE"; omit for every country |
| llm_model | string | – | The model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics. |
No output schema declared.
No examples provided.
get_letter_status Follow a letter ~250
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| conversation_id | string | – | The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics. |
| letter_id | string | yes | – |
| llm_model | string | – | The model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics. |
No output schema declared.
No examples provided.
quote_letter Get a free quote for a letter ~432
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| conversation_id | string | – | The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics. |
| currency | string | – | – |
| document | – | yes | – |
| llm_model | string | – | The model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics. |
| options | object | – | – |
| recipient | object | yes | – |
| sender | object | yes | – |
| service | string | yes | – |
No output schema declared.
No examples provided.
send_feedback Send feedback ~238
Send feedback to the developers of this server: a feature request, or something the user asked for that these tools can't do. The user can also ask you to send feedback directly.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| conversation_id | string | – | The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics. |
| feedback | string | yes | The feedback, in a few sentences: what the user wanted to do and what was missing or went wrong. Leave out names, postal addresses, emails, letter text and other personal data. |
| llm_model | string | – | The model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics. |
No output schema declared.
No examples provided.
send_letter Create the letter and get the payment link ~454
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| conversation_id | string | – | The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics. |
| llm_model | string | – | The model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics. |
| quote_id | string | yes | – |
| webhook_url | string | – | Public https URL notified on each status change |
No output schema declared.
No examples provided.
How do I install the Courio (sendcourio.com) MCP server?
Courio (sendcourio.com) is a hosted endpoint at https://api.sendcourio.com/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.sendcourio.com
claude mcp add --transport http si-courio-courio 'https://api.sendcourio.com/mcp'
What is the Courio (sendcourio.com) MCP server?
Courio (sendcourio.com) is an MCP server listed in the public MCP registry as si.courio/courio. Courio (sendcourio.com): mail real paper letters (standard, registered) worldwide. No account. This page covers its hosted endpoint (https://api.sendcourio.com/mcp).
Is the Courio (sendcourio.com) MCP server safe to use?
Courio (sendcourio.com) scores 67 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 (sendcourio.com) MCP server expose?
Courio (sendcourio.com) exposes 5 tools: get_coverage, quote_letter, send_letter, get_letter_status, send_feedback. Their descriptions and schemas cost roughly 1,705 tokens of context every time the server is loaded.
Does the Courio (sendcourio.com) MCP server require authentication?
No. We connected to Courio (sendcourio.com) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Courio (sendcourio.com) MCP server still maintained?
Courio (sendcourio.com) 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 Courio (sendcourio.com) MCP server?
VerifyMCP ran 13 checks on Courio (sendcourio.com), 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.