me.sendable/sendable
NPM · SENDABLEME-MCP · SCANNED AUG 3
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · sendableme-mcp
claude mcp add me-sendable-sendable -- npx -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": {
"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.
- 2 Aug 26 +43
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 45
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.