dev.multimail/mcp-server
NPM · @MULTIMAIL/MCP-SERVER · 2 COMPONENTS · SCANNED AUG 3
Give your agent its own email address with graduated human oversight, from approval to autonomy.
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 52 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1161 tokens (~193/item across 6 items; 6 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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 · @multimail/mcp-server
claude mcp add dev-multimail-mcp-server -- npx -y @multimail/mcp-server
codex mcp add dev-multimail-mcp-server -- npx -y @multimail/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-multimail-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@multimail/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add dev-multimail-mcp-server --command npx --arg -y --arg @multimail/mcp-server
mcp_servers:
dev-multimail-mcp-server:
command: "npx"
args: ["-y", "@multimail/mcp-server"] {
"mcpServers": {
"dev-multimail-mcp-server": {
"command": "npx",
"args": [
"-y",
"@multimail/mcp-server"
]
}
}
} 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.
- 3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +44
- 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
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: unverified functional
- Licence: MIT functional
- 31 Jul 26 −6
- 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 43
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/@multimail/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 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.
activate_account Activate MultiMail account ~94
Activate a MultiMail account using the activation code from the confirmation email. Accepts the code with or without dashes (e.g. 'SKP-7D2-4V8' or 'SKP7D24V8'). Rate limited to 5 attempts per hour.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The activation code from the confirmation email (e.g. SKP-7D2-4V8) |
No output schema declared.
No examples provided.
create_account Create MultiMail account ~530
Create a new MultiMail account. Requires a solved proof-of-work challenge from request_challenge — the agent must solve the challenge itself (see request_challenge description for algorithm). After calling this tool, the human operator receives a confirmation email with an activation code. Call activate_account with that code to complete signup and receive an API key. The response is always {status: "confirmation_sent"} for privacy — it does not confirm whether the account was actually created or the email already exists. If no activation code arrives within 10 minutes, the email may already have an account (try resend_confirmation or ask the human operator). Slug conflicts return an explicit 409 with suggestions. Other explicit errors (400/429) may come from email validation failures, disposable domain blocking, rate limits, or invalid/expired PoW challenges. Optional DID onboarding: pass agent_did + did_challenge_id + did_signature (all three together, from request_did_challenge) to bind a verifiable Ed25519 agent identity to the account at activation.
| Name | Type | Req | Description |
|---|---|---|---|
| accepted_anti_spam_policy | boolean | yes | Must be true — acceptance of Anti-Spam Policy |
| accepted_operator_agreement | boolean | yes | Must be true — acceptance of Operator Agreement |
| accepted_tos | boolean | yes | Must be true — acceptance of Terms of Service |
| agent_did | string | — | Optional DID binding: your agent's Ed25519 did:key. Must be provided together with did_challenge_id and did_signature (see request_did_challenge). |
| did_challenge_id | string | — | Challenge ID from request_did_challenge (single-use, expires in 5 minutes) |
| did_signature | string | — | Base64url-encoded Ed25519 signature over the MM-DID-BIND:v1 payload (see request_did_challenge for the exact bytes) |
| operator_name | string | yes | Organization or operator name (max 200 characters) |
| oversight_email | string | yes | Email address for oversight notifications and account confirmation |
| oversight_mode | string | — | Initial oversight mode. gated_send (default) = approve outbound. gated_all = approve all. monitored = agent sends freely, operator gets BCC. |
| physical_address | string | — | Physical mailing address for CAN-SPAM compliance |
| pow_solution | object | yes | Solved proof-of-work challenge from request_challenge |
| slug | string | — | URL slug for the account (auto-generated from operator_name if omitted) |
| use_case | string | — | What the agent will use email for (e.g. customer_support, notifications, scheduling) |
No output schema declared.
No examples provided.
request_challenge Request signup challenge ~234
Request a proof-of-work challenge for account creation. Returns an ALTCHA challenge object with fields: algorithm (always SHA-256), challenge (hex hash to match), maxnumber (search space ceiling), salt, and signature. You must solve this before calling create_account. The challenge expires in 5 minutes. To solve: find a number N (0 <= N <= maxnumber) where hex(SHA-256(salt + N)) equals the challenge value. Use the salt string exactly as returned (it may contain query parameters like ?expires=...&) — concatenate it with the decimal string of N, compute SHA-256, and compare the hex digest to challenge. Submit the winning N as pow_solution.number in create_account. Echo back algorithm, challenge, salt, and signature unchanged — do not recompute signature; it is verified server-side. If the challenge expires or is already used, request a new one. Optionally provide oversight_email to calibrate difficulty — consumer email domains may receive easier challenges.
| Name | Type | Req | Description |
|---|---|---|---|
| oversight_email | string | — | Oversight email address (optional, used to calibrate PoW difficulty) |
No output schema declared.
No examples provided.
request_did_challenge Request DID binding challenge ~197
Request an account-binding challenge for DID onboarding (optional identity step before create_account). Send your agent_did (an Ed25519 did:key) and receive {challenge_id, nonce, expires_in}. Sign the UTF-8 bytes of MM-DID-BIND:v1\n<nonce>\n<agent_did>\n<normalize(oversight_email)>\ndid:web:multimail.dev (single LF joins, no trailing newline; normalize = ASCII-trim + ASCII-lowercase) with the DID's Ed25519 private key, base64url-encode the 64-byte signature, then pass agent_did + did_challenge_id + did_signature to create_account. The challenge is single-use and expires in 5 minutes. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_did | string | yes | Your agent's did:key encoding an Ed25519 public key (e.g. did:key:z6Mk...) |
No output schema declared.
No examples provided.
resend_confirmation Resend confirmation code ~70
Resend the activation email with a new code. Requires the oversight email address, not an API key. Use this if the account is stuck in 'pending_operator_confirmation' status. Rate limited to 1 request per 5 minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| oversight_email | string | yes | The oversight email address used during signup |
No output schema declared.
No examples provided.
setup_multimail Set up MultiMail ~36
MultiMail is not configured yet. This tool explains how to get started and give your agent its own email address with human oversight.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.