me.sendable/sendable
NPM · SENDABLEME-MCP · SCANNED SEP 21
Send transactional email from your editor — describe the event, Sendable writes and sends it.
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 96 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 62 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 326 tokens (~108/item across 3 items; 3 tools + 0 resources), lean.Pass
- 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 Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% 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" 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 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
How do I install the me.sendable/sendable MCP server?
me.sendable/sendable runs locally as an npm package, launched with npx -y sendableme-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 · sendableme-mcp
claude mcp add me-sendable-sendable -- npx -y sendableme-mcp
{
"mcpServers": {
"me-sendable-sendable": {
"command": "npx",
"args": [
"-y",
"sendableme-mcp"
]
}
}
} {
"servers": {
"me-sendable-sendable": {
"command": "npx",
"args": [
"-y",
"sendableme-mcp"
]
}
}
} codex mcp add me-sendable-sendable -- npx -y sendableme-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"me-sendable-sendable": {
"type": "local",
"command": [
"npx",
"-y",
"sendableme-mcp"
],
"enabled": true
}
}
} openclaw mcp add me-sendable-sendable --command npx --arg -y --arg sendableme-mcp
mcp_servers:
me-sendable-sendable:
command: "npx"
args: ["-y", "sendableme-mcp"] {
"McpServers": {
"me-sendable-sendable": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"sendableme-mcp"
]
}
}
} assistant mcp add me-sendable-sendable -t stdio -c npx -a -y sendableme-mcp
{
"mcpServers": {
"me-sendable-sendable": {
"command": "npx",
"args": [
"-y",
"sendableme-mcp"
]
}
}
} 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.
- 21 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 20 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 19 Sept 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.
- 17 Sept 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.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 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.
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 21 Sept 2026 · Analysed npm/sendableme-mcp@1.0.3
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 →
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 →
identify ~65
Associate a user id with an email address so you can send by id afterwards. Traits are merged, not replaced, so partial updates are safe.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | – | |
| traits | object | – | Optional extra fields. Flat values only. |
| userId | string | yes | – |
No output schema declared.
No examples provided.
send ~150
Send a transactional email. You describe what happened; Sendable writes the copy and sends it. Data values are inserted verbatim and never rewritten — format them exactly as they should read (e.g. "$99.00", not 99). Use this for anything a user could reasonably want to unsubscribe from.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Flat key/value pairs. Strings, numbers, booleans only — never nested objects or arrays. |
| event | string | yes | What happened, snake_case past tense: order_shipped, trial_ending, invite_accepted. Free-form — there is no list to register against. |
| to | string | yes | Email address, or a user id previously passed to identify. |
No output schema declared.
No examples provided.
send_raw ~111
Send an email with exact copy you supply, skipping composition. Use for password resets, receipts, and security alerts where wording and links must be exact. Unlike send, this bypasses the unsubscribe list, so a user who opted out can still get back into their account. Do not use it to route marketing mail around unsubscribes.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Plain text. Links are sent exactly as written. |
| subject | string | yes | – |
| to | string | yes | Email address or identified user id. |
No output schema declared.
No examples provided.
What is the me.sendable/sendable MCP server?
me.sendable/sendable is an MCP server listed in the public MCP registry as me.sendable/sendable. Send transactional email from your editor, describe the event, Sendable writes and sends it. This page covers its npm package (sendableme-mcp).
Is the me.sendable/sendable MCP server safe to use?
me.sendable/sendable scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 me.sendable/sendable MCP server expose?
me.sendable/sendable exposes 3 tools: send, send_raw, identify. Their descriptions and schemas cost roughly 326 tokens of context every time the server is loaded.
Is the me.sendable/sendable MCP server still maintained?
me.sendable/sendable is still listed as active in the MCP registry. We last reached this channel on 21 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 me.sendable/sendable MCP server under?
me.sendable/sendable declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.