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.

Paper Plane Post

REMOTE · API.PAPERPLANEPOST.COM

Create and send an AI-illustrated postcard anywhere in the world

+4 this week 67 Trust /100

Last scanned (10 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

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 Usability33
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 689 tokens (~229/item across 3 items; 2 tools + 1 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 Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
  • 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
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1
    • Tool coverage: 100% → 88% ▼ functional
    • Schema quality: 304 → 229 ▲ functional
    • Schema quality: fair → good functional
    • New tool “show_postcard” functional
  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 −7
    • Tool “start_postcard” rewrote its description, which is the text the model reads security
    • Schema quality: 425 → 304 ▲ functional
    • The server now declares the “resources” capability functional
    • First check of Capabilities: pass functional
    • First check of Schema quality: 0 functional
    • Schema quality: excellent → fair functional
    • New resource “postcard-handoff” functional
    • “start_postcard” added an optional parameter “is_ai_generated” cosmetic
    • “start_postcard” added an optional parameter “photo” cosmetic
    • “start_postcard” reworded the description of “photo_base64” cosmetic
    • Tool “start_postcard” changed its title: Start a postcard → Postcard Maker cosmetic
  • 24 Oct 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.

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.paperplanepost.com/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=paperplanepost.com CN=WE1,O=Google Trust Services,C=US 28 Sept 2026 27 Dec 2026 ECDSA 256 ECDSA-SHA256 e22564ec3eb937360e533ed35e705b59
SANs: paperplanepost.com, api.paperplanepost.com, *.api.paperplanepost.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 api.paperplanepost.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
paperplanepost.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://api.paperplanepost.com/v1/mcp Verified 200
http (plaintext) http://api.paperplanepost.com/v1/mcp Inconclusive 405
MCP tools · 2 exposed · ~683 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
show_postcard ~80

Display the Finish your postcard button for an existing unpaid draft URL returned by start_postcard, including after the Claude skill's file-transfer helper. Does not create a draft, read its contents, charge, or mail anything. Only use the exact returned URL; never invent one. This cannot look up orders or delivery status.

NameTypeReqDescription
urlstringyes–
NameTypeReqDescription
urlstringyesThe link the person opens to finish and pay for the postcard.

No examples provided.

start_postcard ~603

Start a Paper Plane Post postcard: a photo printed on a 4×6 card, with an optional illustrated version of it, mailed first class for $7 with postage included. Mails from the US to 194 countries; the address country is an ISO 3166-1 alpha-2 code. Use photo for an uploaded or ChatGPT-generated image. Other clients can send photo_base64 encoded from the file itself, or photo_url if the image is already online. If no image is available, ask for an uploaded photo or public image URL. Do not call this tool or invent image data. Set is_ai_generated to true for an image you generated or know was AI-generated; its illustration is made only if the person selects Illustrated on the website. Include the note and recipient address if the person has supplied them. If either is missing, start the postcard immediately without asking for it; the person can complete it on the website. Returns a link for the person to open: they see their photo on the card, finish the note and address, can choose the illustrated version, and pay on the website. Nothing is charged or mailed until they do. Never ask for payment details. The link expires after about a week. This tool only starts postcards. It cannot retrieve orders or delivery status; explain that limitation for lookup requests instead of calling it. On a busy day the tool may first answer with a short challenge of four questions to solve and send back in the challenge argument; the proof-of-work question needs a code tool.

NameTypeReqDescription
challengeobject–Only after this tool answered with a challenge: its id, and your answers to its four questions in the order they were asked, each as a short string. Solve the proof-of-work question with a code tool;…
is_ai_generatedboolean–Set true when the supplied image was already AI-generated. The website keeps the original and only generates an illustrated version if the person selects Illustrated.
notestring–The note for the back of the card, if the person told you what to say. Up to 350 characters.
photoobject–The uploaded photo or image created in this conversation. Use the actual file supplied by ChatGPT.
photo_base64string–For clients without native file transfer: the photo file's own bytes as base64 or a data: URL, read and encoded with a file or code tool. JPEG, PNG, WebP or HEIC, up to about 10 MB. Never invent base…
photo_urlstring–A public https:// URL of the photo. Use this only when the photo is already online and you don't have the file.
recipientobject–Whatever you know of the recipient's mailing address. The person completes and checks it before paying.
NameTypeReqDescription
urlstringyesThe link the person opens to finish and pay for the postcard.

No examples provided.

Install

How do I install the Paper Plane Post MCP server?

Paper Plane Post is a hosted endpoint at https://api.paperplanepost.com/v1/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.paperplanepost.com

# add to Claude Code
claude mcp add --transport http com-paperplanepost-office 'https://api.paperplanepost.com/v1/mcp'
Common questions

What is the Paper Plane Post MCP server?

Paper Plane Post is an MCP server listed in the public MCP registry as com.paperplanepost/office. Create and send an AI-illustrated postcard anywhere in the world. This page covers its hosted endpoint (https://api.paperplanepost.com/v1/mcp).

Is the Paper Plane Post MCP server safe to use?

Paper Plane Post 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 Paper Plane Post MCP server expose?

Paper Plane Post exposes 2 tools: start_postcard, show_postcard. Their descriptions and schemas cost roughly 683 tokens of context every time the server is loaded.

Does the Paper Plane Post MCP server require authentication?

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

Is the Paper Plane Post MCP server still maintained?

Paper Plane Post 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.