io.github.iancollins27/mailsnail
NPM · MAILSNAIL · SCANNED SEP 20
Send USPS letters, postcards & certified mail from any agent. No signup; pay-per-piece via Stripe.
Available components
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 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 68 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 911 tokens (~130/item across 7 items; 7 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 37% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_letter" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- 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
How do I install the io.github.iancollins27/mailsnail MCP server?
io.github.iancollins27/mailsnail runs locally as an npm package, launched with npx -y mailsnail. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mailsnail
claude mcp add iancollins27-mailsnail -- npx -y mailsnail
{
"mcpServers": {
"iancollins27-mailsnail": {
"command": "npx",
"args": [
"-y",
"mailsnail"
]
}
}
} {
"servers": {
"iancollins27-mailsnail": {
"command": "npx",
"args": [
"-y",
"mailsnail"
]
}
}
} codex mcp add iancollins27-mailsnail -- npx -y mailsnail
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"iancollins27-mailsnail": {
"type": "local",
"command": [
"npx",
"-y",
"mailsnail"
],
"enabled": true
}
}
} openclaw mcp add iancollins27-mailsnail --command npx --arg -y --arg mailsnail
mcp_servers:
iancollins27-mailsnail:
command: "npx"
args: ["-y", "mailsnail"] {
"McpServers": {
"iancollins27-mailsnail": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mailsnail"
]
}
}
} assistant mcp add iancollins27-mailsnail -t stdio -c npx -a -y mailsnail
{
"mcpServers": {
"iancollins27-mailsnail": {
"command": "npx",
"args": [
"-y",
"mailsnail"
]
}
}
} 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.
- 20 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.
- 18 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.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 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.
- 11 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 10 Sept 26 −3
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.83 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/mailsnail@0.6.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 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_letter ~35
Cancel a letter before it enters production. Cancellation windows are short and provider-specific.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Provider letter/job id. |
No output schema declared.
No examples provided.
get_letter ~30
Fetch the status of a previously sent letter by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Provider letter/job id. |
No output schema declared.
No examples provided.
list_letters ~47
List recent letters (Lob only — Click2Mail does not expose a list endpoint).
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | – |
| before | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
preview_letter ~212
Generate a PROOF of a letter WITHOUT charging or mailing. Returns `proof_url` (a viewable PDF of exactly what will be printed and mailed, including the address cover sheet), the CASS-verified recipient address, the exact price, and a `draft_id`. Best practice: call this FIRST, show the user the proof_url and price, get explicit confirmation, then call send_letter with the returned draft_id + a payment_token. Managed/gateway mode only.
| Name | Type | Req | Description |
|---|---|---|---|
| body_text | string | – | Plain text body. Rendered to a letter-sized PDF server-side. Managed/gateway provider only. |
| color | boolean | – | – |
| description | string | – | – |
| double_sided | boolean | – | – |
| extra_service | string | – | Adds tracking. `certified` for legal/compliance mail. |
| file_url | string | – | Public URL to a pre-rendered PDF letter. Letter-size 8.5x11 expected. |
| from | – | yes | – |
| to | object | yes | – |
No output schema declared.
No examples provided.
send_letter ~355
Send a physical letter via USPS. RECOMMENDED FLOW: first call preview_letter, show the user the returned proof_url + price, get explicit confirmation, then call send_letter with the returned `draft_id` and a `payment_token` — this charges and mails exactly the proofed letter. You may also send one-shot by providing the full letter (to, from, and body_text or file_url) plus payment_token, without a draft_id. `body_text` (plain text, rendered server-side) is managed/gateway-mode only; click2mail/lob require file_url. Use `extra_service: 'certified'` for certified mail (recommended for legal notices).
| Name | Type | Req | Description |
|---|---|---|---|
| body_text | string | – | Plain text body of the letter. Newlines preserved. Rendered to a letter-sized PDF server-side. Managed/gateway provider only. |
| color | boolean | – | – |
| description | string | – | – |
| double_sided | boolean | – | – |
| draft_id | string | – | Confirm a letter previewed via preview_letter. Provide this plus payment_token to charge and mail exactly that proof. Omit for a one-shot send. |
| extra_service | string | – | Adds tracking. `certified` is the most common; useful for legal/compliance mail. |
| file_url | string | – | Public URL to a pre-rendered PDF letter. Letter-size 8.5x11 expected. |
| from | – | – | – |
| payment_token | string | – | Stripe Shared Payment Token (spt_...). Required when MAIL_PROVIDER=managed. If omitted in managed mode, the tool returns a payment_required error with the quoted price so you can mint an SPT and retr… |
| to | object | – | – |
No output schema declared.
No examples provided.
send_postcard ~163
Send a physical postcard. Provide a public URL to a PDF (front + back combined for Click2Mail; separate front/back for Lob).
| Name | Type | Req | Description |
|---|---|---|---|
| back_url | string | – | URL to PDF for the postcard back. Required for Lob; ignored for Click2Mail. |
| description | string | – | – |
| from | – | yes | – |
| front_url | string | yes | URL to PDF for the postcard front (or combined front+back for Click2Mail). |
| payment_token | string | – | Stripe Shared Payment Token (spt_...). Required when MAIL_PROVIDER=managed. If omitted in managed mode, the tool returns a payment_required error with the quoted price so you can mint an SPT and retr… |
| size | string | – | – |
| to | object | yes | – |
No output schema declared.
No examples provided.
verify_address ~69
Verify and normalize a US mailing address. Run this on user-provided addresses before sending mail.
| Name | Type | Req | Description |
|---|---|---|---|
| address_city | string | – | – |
| address_line1 | string | yes | – |
| address_line2 | string | – | – |
| address_state | string | – | – |
| address_zip | string | – | – |
No output schema declared.
No examples provided.
What is the io.github.iancollins27/mailsnail MCP server?
io.github.iancollins27/mailsnail is an MCP server listed in the public MCP registry as io.github.iancollins27/mailsnail. Send USPS letters, postcards & certified mail from any agent. No signup; pay-per-piece via Stripe. This page covers its npm package (mailsnail).
Is the io.github.iancollins27/mailsnail MCP server safe to use?
io.github.iancollins27/mailsnail scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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.iancollins27/mailsnail MCP server expose?
io.github.iancollins27/mailsnail exposes 7 tools: verify_address, preview_letter, send_letter, send_postcard, get_letter, and 2 more. Their descriptions and schemas cost roughly 911 tokens of context every time the server is loaded.
Is the io.github.iancollins27/mailsnail MCP server still maintained?
io.github.iancollins27/mailsnail is still listed as active in the MCP registry. We last reached this channel on 20 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.iancollins27/mailsnail MCP server under?
io.github.iancollins27/mailsnail declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.