# Courio (sendcourio.com) (remote · api.sendcourio.com)

Courio (sendcourio.com): mail real paper letters (standard, registered) worldwide. No account.

- Trust score: 67/100 (medium)
- Change this week: −2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.sendcourio.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/si-courio-courio/api-2.md), [page](https://verifymcp.io/servers/si-courio-courio/api-2)

## Channel facts

- Endpoint: `https://api.sendcourio.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 12 days we've observed: 0 tool removals, 5 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 69% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http si-courio-courio 'https://api.sendcourio.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "si-courio-courio": {
      "url": "https://api.sendcourio.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "si-courio-courio": {
      "type": "http",
      "url": "https://api.sendcourio.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.si-courio-courio]
url = "https://api.sendcourio.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "si-courio-courio": {
      "type": "remote",
      "url": "https://api.sendcourio.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add si-courio-courio --url 'https://api.sendcourio.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  si-courio-courio:
    url: "https://api.sendcourio.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "si-courio-courio": {
      "Transport": "http",
      "Url": "https://api.sendcourio.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add si-courio-courio -t streamable-http -u 'https://api.sendcourio.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "si-courio-courio": {
      "type": "http",
      "url": "https://api.sendcourio.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-16 (score 67, +1)

- [security regression] A breaking change shipped without a version bump: still 1.0.1
- [functional regression] “send_feedback” added a required parameter “feedback”, so existing callers break
- [functional regression] “send_feedback” dropped the required parameter “capability”
- [functional improvement] Tool coverage: 60% → 69%
- [cosmetic] “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

### 2026-11-15 (score 66, −3)

- [security regression] Stability: 0.17 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.1
- [functional regression] Schema quality: 198 → 348
- [functional regression] “send_feedback” added a required parameter “context”, so existing callers break
- [functional regression] “get_coverage” added a required parameter “context”, so existing callers break
- [functional regression] “get_letter_status” added a required parameter “context”, so existing callers break
- [functional regression] “quote_letter” added a required parameter “context”, so existing callers break
- [functional regression] “send_letter” added a required parameter “context”, so existing callers break
- [functional improvement] Tool coverage: 20% → 60%
- [cosmetic] “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”

### 2026-11-14 (score 69, +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.

### 2026-11-12 (score 68, +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.

### 2026-11-10 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 66)

First indexed and scored.

## MCP tools (5)

### `get_coverage` (~331 tokens)

Check coverage and indicative prices

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).

Input parameters:

- `context` (string, required): 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.

### `quote_letter` (~432 tokens)

Get a free quote for a letter

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.

Input parameters:

- `context` (string, required): 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` (required)
- `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, required)
- `sender` (object, required)
- `service` (string, required)

### `send_letter` (~454 tokens)

Create the letter and get the payment link

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.

Input parameters:

- `context` (string, required): 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, required)
- `webhook_url` (string): Public https URL notified on each status change

### `get_letter_status` (~250 tokens)

Follow a letter

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.

Input parameters:

- `context` (string, required): 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, required)
- `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.

### `send_feedback` (~238 tokens)

Send feedback

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.

Input parameters:

- `context` (string, required): 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, required): 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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/si-courio-courio/api-2#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 67
- 2026-11-19: 67
- 2026-11-18: 67
- 2026-11-17: 67
- 2026-11-16: 67
- 2026-11-15: 66
- 2026-11-14: 69
- 2026-11-13: 68
- 2026-11-12: 68
- 2026-11-11: 67
- 2026-11-10: 67
- 2026-11-09: 66

## Common questions

### 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.

## Links

- Remote endpoint: https://api.sendcourio.com/mcp
- Website: https://sendcourio.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/si-courio-courio/api-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/si-courio-courio/api-2/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/si-courio-courio/api-2.json
- HTML version of this page: https://verifymcp.io/servers/si-courio-courio/api-2
