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.

dev.multimail/mcp-server

NPM · @MULTIMAIL/MCP-SERVER · 2 COMPONENTS

Give your agent its own email address with graduated human oversight, from approval to autonomy.

0 this week 78 Trust /100

Last scanned (19 hours ago)

Scores higher than 59% of npm servers

Category Communication

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability68
  • 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 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.

  • 8 Nov 26 −2
    • Stability: pass → 0.87 functional
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
  • 25 Oct 26 −1
    • Stability: pass → 0.93 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
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 21 Nov 2026 · Analysed npm/@multimail/mcp-server@0.13.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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~1,161 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
activate_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.

NameTypeReqDescription
codestringyesThe activation code from the confirmation email (e.g. SKP-7D2-4V8)

No output schema declared.

No examples provided.

create_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.

NameTypeReqDescription
accepted_anti_spam_policybooleanyesMust be true — acceptance of Anti-Spam Policy
accepted_operator_agreementbooleanyesMust be true — acceptance of Operator Agreement
accepted_tosbooleanyesMust be true — acceptance of Terms of Service
agent_didstring–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_idstring–Challenge ID from request_did_challenge (single-use, expires in 5 minutes)
did_signaturestring–Base64url-encoded Ed25519 signature over the MM-DID-BIND:v1 payload (see request_did_challenge for the exact bytes)
operator_namestringyesOrganization or operator name (max 200 characters)
oversight_emailstringyesEmail address for oversight notifications and account confirmation
oversight_modestring–Initial oversight mode. gated_send (default) = approve outbound. gated_all = approve all. monitored = agent sends freely, operator gets BCC.
physical_addressstring–Physical mailing address for CAN-SPAM compliance
pow_solutionobjectyesSolved proof-of-work challenge from request_challenge
slugstring–URL slug for the account (auto-generated from operator_name if omitted)
use_casestring–What the agent will use email for (e.g. customer_support, notifications, scheduling)

No output schema declared.

No examples provided.

request_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.

NameTypeReqDescription
oversight_emailstring–Oversight email address (optional, used to calibrate PoW difficulty)

No output schema declared.

No examples provided.

request_did_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.

NameTypeReqDescription
agent_didstringyesYour agent's did:key encoding an Ed25519 public key (e.g. did:key:z6Mk...)

No output schema declared.

No examples provided.

resend_confirmation ~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.

NameTypeReqDescription
oversight_emailstringyesThe oversight email address used during signup

No output schema declared.

No examples provided.

setup_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.

Install

How do I install the dev.multimail/mcp-server server?

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

npm · @multimail/mcp-server

# add to Claude Code
claude mcp add dev-multimail-mcp-server -- npx -y @multimail/mcp-server
Common questions

What is the dev.multimail/mcp-server server?

dev.multimail/mcp-server is listed in the public MCP registry as dev.multimail/mcp-server. Give your agent its own email address with graduated human oversight, from approval to autonomy. This page covers its npm package (@multimail/mcp-server).

Is the dev.multimail/mcp-server server safe to use?

dev.multimail/mcp-server scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 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 dev.multimail/mcp-server server expose?

dev.multimail/mcp-server exposes 6 tools: setup_multimail, request_challenge, request_did_challenge, create_account, activate_account, resend_confirmation. Their descriptions and schemas cost roughly 1,161 tokens of context every time the server is loaded.

Is the dev.multimail/mcp-server server still maintained?

dev.multimail/mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 November 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 dev.multimail/mcp-server server under?

dev.multimail/mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the dev.multimail/mcp-server server?

VerifyMCP ran 16 checks on dev.multimail/mcp-server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.