Sendpaper
REMOTE · SENDMYPAPER.COM
Your agent sends real postcards and letters. You approve; we print and mail.
Available components
Last scanned (20 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 4 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (pay_order). See how to fix → View diagnostics → Fail
- 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1310 tokens (~218/item across 6 items; 6 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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
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 7 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
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.
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 0
- “create_letter” reworded the description of “from” cosmetic
- “create_postcard” reworded the description of “from” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Probed https://sendmypaper.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sendmypaper.com | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 9bb64baa0c99a66d1312fc67fb78cbd0 |
| SANs: sendmypaper.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sendmypaper.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sendmypaper.com. | absent | 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://sendmypaper.com/mcp | Verified | 200 | |
| http (plaintext) | http://sendmypaper.com/mcp | HTTPS enforced | 301 | https://sendmypaper.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 →
cancel_order Cancel an unpaid order ~44
Cancel an order that has not been paid yet. Paid orders can be cancelled by emailing support before they are printed.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | Order id, ord_… |
| Name | Type | Req | Description |
|---|---|---|---|
| batch | object | – | Present when the order was created with recipients: the whole group. The top-level fields describe the first recipient's order; use batch.price and batch.checkout_url for the total and payment. |
| certified | string | yes | none, certified or certified_return_receipt |
| checkout_url | string|null | yes | Where the user pays; null once paid or cancelled |
| discount | – | yes | First-order discount, already taken off price; null when none applies |
| id | string | yes | Order id, ord_… |
| object | string | yes | – |
| order_url | string | yes | Order status page |
| orders | array | – | Every order in the group, when created with recipients |
| preview_image_url | string | – | PNG picture of the piece (postcard front and back, or the letter's first page) to show the user |
| preview_url | string | yes | Exact print preview |
| price | object | yes | – |
| product | string | yes | Product id, e.g. postcard_4x6 or letter_certified |
| product_name | string | yes | – |
| status | string | yes | awaiting_payment, paid, printing, mailed, cancelled or refunded |
| status_detail | string | yes | Plain-English status to show the user |
| tracking | – | yes | USPS tracking, for Certified Mail once printed |
No examples provided.
create_letter Create a letter ~404
Create a printed letter order (8.5x11, mailed in a #10 envelope) and get a payment link. Either write it (content.body, up to ~3 pages, optional photo) or mail the user's own PDF (content.pdf_url, a public https link, up to 6 pages). Set certified to "certified" for USPS Certified Mail with tracking and proof of delivery, or "certified_return_receipt" to add the recipient's signature; use these when the user needs proof (tax notice replies, lease notices, disputes, demand letters). Or set express for USPS Priority Mail (not with certified). Prices: get_pricing. Mails only after the user pays.
| Name | Type | Req | Description |
|---|---|---|---|
| certified | string | – | USPS Certified Mail. "certified": tracking number and proof of mailing and delivery. "certified_return_receipt": adds the recipient's signature as proof of delivery, which landlords, courts and agenc… |
| content | object | yes | The letter: body text (optionally with a photo) or your own PDF |
| customer_email | string | – | Where to send the receipt and status updates |
| express | boolean | – | Send by express (USPS Priority Mail, usually 2–3 days, with tracking) for an extra charge; see get_pricing. Not available with certified. |
| from | object | yes | Return address; printed on the mail piece. May be outside the US (set country) |
| idempotency_key | string | – | Any unique string; retrying with the same key returns the original order instead of creating a duplicate |
| recipients | array | – | Send the same piece to several people: 2-25 US addresses, used INSTEAD of to. Each gets their own order and tracking; one payment covers all. |
| to | object | – | Recipient's US mailing address (or use recipients for several people) |
| Name | Type | Req | Description |
|---|---|---|---|
| batch | object | – | Present when the order was created with recipients: the whole group. The top-level fields describe the first recipient's order; use batch.price and batch.checkout_url for the total and payment. |
| certified | string | yes | none, certified or certified_return_receipt |
| checkout_url | string|null | yes | Where the user pays; null once paid or cancelled |
| discount | – | yes | First-order discount, already taken off price; null when none applies |
| id | string | yes | Order id, ord_… |
| object | string | yes | – |
| order_url | string | yes | Order status page |
| orders | array | – | Every order in the group, when created with recipients |
| preview_image_url | string | – | PNG picture of the piece (postcard front and back, or the letter's first page) to show the user |
| preview_url | string | yes | Exact print preview |
| price | object | yes | – |
| product | string | yes | Product id, e.g. postcard_4x6 or letter_certified |
| product_name | string | yes | – |
| status | string | yes | awaiting_payment, paid, printing, mailed, cancelled or refunded |
| status_detail | string | yes | Plain-English status to show the user |
| tracking | – | yes | USPS tracking, for Certified Mail once printed |
No examples provided.
create_postcard Create a postcard ~324
Create a postcard order (4x6, 6x9 or 6x11) and get a payment link. Front layouts: a big headline on a color, one photo, a photo with a caption, or a collage of 2-4 photos; the back carries the message (handwriting, serif or sans) and addresses. Set express for USPS Priority Mail (2-3 days, tracked). Mails only after the user pays.
| Name | Type | Req | Description |
|---|---|---|---|
| content | object | yes | Front (an image URL or a headline) and the message on the back |
| customer_email | string | – | Where to send the receipt and status updates |
| express | boolean | – | Send by express (USPS Priority Mail, usually 2–3 days, with tracking) for an extra charge; see get_pricing. Not available with certified. |
| from | object | yes | Return address; printed on the mail piece. May be outside the US (set country) |
| idempotency_key | string | – | Any unique string; retrying with the same key returns the original order instead of creating a duplicate |
| recipients | array | – | Send the same piece to several people: 2-25 US addresses, used INSTEAD of to. Each gets their own order and tracking; one payment covers all. |
| size | string | – | Postcard size: 4x6, 6x9 or 6x11 (see get_pricing for prices) |
| to | object | – | Recipient's US mailing address (or use recipients for several people) |
| Name | Type | Req | Description |
|---|---|---|---|
| batch | object | – | Present when the order was created with recipients: the whole group. The top-level fields describe the first recipient's order; use batch.price and batch.checkout_url for the total and payment. |
| certified | string | yes | none, certified or certified_return_receipt |
| checkout_url | string|null | yes | Where the user pays; null once paid or cancelled |
| discount | – | yes | First-order discount, already taken off price; null when none applies |
| id | string | yes | Order id, ord_… |
| object | string | yes | – |
| order_url | string | yes | Order status page |
| orders | array | – | Every order in the group, when created with recipients |
| preview_image_url | string | – | PNG picture of the piece (postcard front and back, or the letter's first page) to show the user |
| preview_url | string | yes | Exact print preview |
| price | object | yes | – |
| product | string | yes | Product id, e.g. postcard_4x6 or letter_certified |
| product_name | string | yes | – |
| status | string | yes | awaiting_payment, paid, printing, mailed, cancelled or refunded |
| status_detail | string | yes | Plain-English status to show the user |
| tracking | – | yes | USPS tracking, for Certified Mail once printed |
No examples provided.
get_order Check an order ~37
Get the status of a postcard or letter order by id (ord_...).
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | Order id, ord_… |
| Name | Type | Req | Description |
|---|---|---|---|
| batch | object | – | Present when the order was created with recipients: the whole group. The top-level fields describe the first recipient's order; use batch.price and batch.checkout_url for the total and payment. |
| certified | string | yes | none, certified or certified_return_receipt |
| checkout_url | string|null | yes | Where the user pays; null once paid or cancelled |
| discount | – | yes | First-order discount, already taken off price; null when none applies |
| id | string | yes | Order id, ord_… |
| object | string | yes | – |
| order_url | string | yes | Order status page |
| orders | array | – | Every order in the group, when created with recipients |
| preview_image_url | string | – | PNG picture of the piece (postcard front and back, or the letter's first page) to show the user |
| preview_url | string | yes | Exact print preview |
| price | object | yes | – |
| product | string | yes | Product id, e.g. postcard_4x6 or letter_certified |
| product_name | string | yes | – |
| status | string | yes | awaiting_payment, paid, printing, mailed, cancelled or refunded |
| status_detail | string | yes | Plain-English status to show the user |
| tracking | – | yes | USPS tracking, for Certified Mail once printed |
No examples provided.
get_pricing Get prices ~29
List mail products and prices (USD, printing + USPS First-Class postage included, US addresses only).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| express | object | yes | Surcharge for express delivery |
| first_order_discount | object | yes | Current first-order discount (0 when none) |
| letter_photo | object | yes | Surcharge for a letter printed in color (a photo, or a PDF with color on) |
| payment | object | yes | – |
| pdf_letters | object | yes | Mailing your own PDF as a letter |
| products | array | yes | – |
No examples provided.
pay_order Pay for an order ~118
Pay for an unpaid order with a Stripe shared payment token (spt_…) the user approved, scoped to at least the order amount in USD. For an order created with recipients, this pays for the whole group at once (scope the token to batch.price). On success the order is paid and goes to print. Use only after the user approved the purchase.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | Order id from create_postcard or create_letter, ord_… |
| shared_payment_token | string | yes | Stripe shared payment token, spt_… |
| Name | Type | Req | Description |
|---|---|---|---|
| batch | object | – | Present when the order was created with recipients: the whole group. The top-level fields describe the first recipient's order; use batch.price and batch.checkout_url for the total and payment. |
| certified | string | yes | none, certified or certified_return_receipt |
| checkout_url | string|null | yes | Where the user pays; null once paid or cancelled |
| discount | – | yes | First-order discount, already taken off price; null when none applies |
| id | string | yes | Order id, ord_… |
| object | string | yes | – |
| order_url | string | yes | Order status page |
| orders | array | – | Every order in the group, when created with recipients |
| preview_image_url | string | – | PNG picture of the piece (postcard front and back, or the letter's first page) to show the user |
| preview_url | string | yes | Exact print preview |
| price | object | yes | – |
| product | string | yes | Product id, e.g. postcard_4x6 or letter_certified |
| product_name | string | yes | – |
| status | string | yes | awaiting_payment, paid, printing, mailed, cancelled or refunded |
| status_detail | string | yes | Plain-English status to show the user |
| tracking | – | yes | USPS tracking, for Certified Mail once printed |
No examples provided.
How do I install the Sendpaper MCP server?
Sendpaper is a hosted endpoint at https://sendmypaper.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 · sendmypaper.com
claude mcp add --transport http ryan-tish-sendpaper 'https://sendmypaper.com/mcp'
What is the Sendpaper MCP server?
Sendpaper is an MCP server listed in the public MCP registry as io.github.ryan-tish/sendpaper. Your agent sends real postcards and letters. You approve; we print and mail. This page covers its hosted endpoint (https://sendmypaper.com/mcp).
Is the Sendpaper MCP server safe to use?
Sendpaper scores 76 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 Sendpaper MCP server expose?
Sendpaper exposes 6 tools: get_pricing, create_postcard, create_letter, pay_order, get_order, cancel_order. Their descriptions and schemas cost roughly 956 tokens of context every time the server is loaded.
Does the Sendpaper MCP server require authentication?
No. We connected to Sendpaper without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sendpaper MCP server still maintained?
Sendpaper is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.