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.

io.github.coopergwrenn/postals-mcp

NPM · POSTALS-MCP · SCANNED SEP 25

Send physical handwritten postcards from any AI agent. Real pen & ink, USPS, $4.99/card.

Available components

+1 this week 76 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability40
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 622 tokens (~311/item across 2 items; 2 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 Management87
  • Stability observed for 26 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
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 3 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
Install

How do I install the io.github.coopergwrenn/postals-mcp server?

io.github.coopergwrenn/postals-mcp runs locally as an npm package, launched with npx -y postals-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · postals-mcp

# add to Claude Code
claude mcp add coopergwrenn-postals-mcp -- npx -y postals-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "coopergwrenn-postals-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "postals-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "coopergwrenn-postals-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "postals-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add coopergwrenn-postals-mcp -- npx -y postals-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "coopergwrenn-postals-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "postals-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add coopergwrenn-postals-mcp --command npx --arg -y --arg postals-mcp
# ~/.hermes/config.yaml
mcp_servers:
  coopergwrenn-postals-mcp:
    command: "npx"
    args: ["-y", "postals-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "coopergwrenn-postals-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "postals-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add coopergwrenn-postals-mcp -t stdio -c npx -a -y postals-mcp
// mcp.json
{
  "mcpServers": {
    "coopergwrenn-postals-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "postals-mcp"
      ]
    }
  }
}
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.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 −3
    • Stability: pass → 0.83 functional
  • 23 Sept 26 +1
    • Stability: 0.97 → pass security
  • 21 Sept 26 +1

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

  • 19 Sept 26 +1

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

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 25 Sept 2026 · Analysed npm/postals-mcp@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~542 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
generate_message ~175

Generate a personalized handwritten message for a postcard based on context about the recipient. Returns a ready-to-use message you can pass directly to send_postcard. Uses AI if Cloudflare credentials are configured (CLOUDFLARE_ACCOUNT_ID + CLOUDFLARE_API_TOKEN); otherwise returns a structured prompt you can use to compose the message yourself.

NameTypeReqDescription
max_charsnumber–Max character count for the message
recipient_contextstringyesWho the recipient is and why you're writing. Example: 'John Smith, homeowner at 123 Oak St. Sending a before/after postcard showing what a pool would look like in his backyard.'
sender_contextstring–Who is sending the card. Example: 'Blue Wave Pools — local pool builder in Austin, TX'
tonestring–Message tone

No output schema declared.

No examples provided.

send_postcard ~367

Send a physical handwritten postcard to a US mailing address. Postals prints it with real robotic handwriting (pen and ink) and mails it via USPS. Delivery in 3-5 business days. Cost: $4.99 per card. Provide the recipient's address, a message (max 400 chars), and optionally an image URL for the card front. If no image is provided, uses the configured default card.

NameTypeReqDescription
front_image_urlstring–Public HTTPS URL of the image for the card front (PNG or JPEG, landscape 7x5 preferred). If omitted, uses POSTALS_DEFAULT_CARD_IMAGE.
handwriting_stylestring–Handwriting font name. Default: "Joyful Jennifer". Other options depend on your Handwrytten account.
idempotency_keystring–Unique key to prevent duplicate sends on retries. If a prior send with this key succeeded, returns the original result without sending a new card. Recommended for autonomous agents.
messagestringyesThe handwritten message for the back of the card. Max 400 characters. Keep it personal and concise.
return_addressobject–Sender's return address. If omitted, uses POSTALS_SENDER_* env defaults.
to_addressstringyesStreet address line 1
to_address_2string–Street address line 2 (apt, suite, etc.)
to_citystringyesCity
to_namestringyesRecipient's full name (e.g. 'Jane Smith')
to_statestringyesTwo-letter US state code (e.g. CA, NY, TX)
to_zipstringyes5-digit ZIP code (e.g. 78701 or 78701-1234)

No output schema declared.

No examples provided.

Common questions

What is the io.github.coopergwrenn/postals-mcp server?

io.github.coopergwrenn/postals-mcp is listed in the public MCP registry as io.github.coopergwrenn/postals-mcp. Send physical handwritten postcards from any AI agent. Real pen & ink, USPS, $4.99/card. This page covers its npm package (postals-mcp).

Is the io.github.coopergwrenn/postals-mcp server safe to use?

io.github.coopergwrenn/postals-mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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 io.github.coopergwrenn/postals-mcp server expose?

io.github.coopergwrenn/postals-mcp exposes 2 tools: send_postcard, generate_message. Their descriptions and schemas cost roughly 542 tokens of context every time the server is loaded.

Is the io.github.coopergwrenn/postals-mcp server still maintained?

io.github.coopergwrenn/postals-mcp is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.coopergwrenn/postals-mcp server under?

io.github.coopergwrenn/postals-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.