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.

Atomic Mail

NPM · @ATOMICMAIL/MCP-MODELCONTEXTPROTOCOL · 2 COMPONENTS · SCANNED SEP 22

Programmable email inbox for AI agents — JMAP, PoW auth, stdio MCP server.

Available components

remote · mcp.atomicmail.ai 39 npm · @atomicmail/mcp-modelcontextprotocol 79
0 this week 79 Trust /100
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 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 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1173 tokens (~391/item across 3 items; 3 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 Management80
  • Stability observed for 24 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
Install

How do I install the Atomic Mail MCP server?

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

npm · @atomicmail/mcp-modelcontextprotocol

# add to Claude Code
claude mcp add atomic-mail-mcp -- npx -y @atomicmail/mcp-modelcontextprotocol
// .cursor/mcp.json
{
  "mcpServers": {
    "atomic-mail-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@atomicmail/mcp-modelcontextprotocol"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "atomic-mail-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@atomicmail/mcp-modelcontextprotocol"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add atomic-mail-mcp -- npx -y @atomicmail/mcp-modelcontextprotocol
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "atomic-mail-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@atomicmail/mcp-modelcontextprotocol"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add atomic-mail-mcp --command npx --arg -y --arg @atomicmail/mcp-modelcontextprotocol
# ~/.hermes/config.yaml
mcp_servers:
  atomic-mail-mcp:
    command: "npx"
    args: ["-y", "@atomicmail/mcp-modelcontextprotocol"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "atomic-mail-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@atomicmail/mcp-modelcontextprotocol"
      ]
    }
  }
}
# add to Vellum
assistant mcp add atomic-mail-mcp -t stdio -c npx -a -y @atomicmail/mcp-modelcontextprotocol
// mcp.json
{
  "mcpServers": {
    "atomic-mail-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@atomicmail/mcp-modelcontextprotocol"
      ]
    }
  }
}
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.

  • 22 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 21 Sept 26 0
    • Stability: 0.97 → pass security
  • 20 Sept 26 +1
    • Package version: 0.3.26 → 0.3.27 functional
  • 19 Sept 26 +11
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.86 ▲ functional
  • 18 Sept 26 −10
    • Known CVEs: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.87 → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Dependency health: 0.86 → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Package version: 0.3.26 → 0.3.27 functional
  • 16 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.

  • 15 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 14 Sept 26 0
    • Stability: 0.97 → pass 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 22 Sept 2026 · Analysed npm/@atomicmail/mcp-modelcontextprotocol@0.3.27

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 98 packages
Packages resolved 98
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~646 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
help ~94

Built-in agent docs — call early and often, even if you know JMAP. Topics: overview, installation, auth, jmap_cheatsheet, tools, presets, cron, multi_account, troubleshooting, readme. Omit topic for overview; use presets before jmap_request, cron after register, troubleshooting when stuck.

NameTypeReqDescription
topicstring–Topic name; omit for overview. Use readme for package README.md.

No output schema declared.

No examples provided.

jmap_request ~250

JMAP method-call batch with automatic auth. Exactly one of: `ops` (JSON string: methodCalls array or full envelope) or `ops_file` (preset path; relative to credential directory). `$VAR` substitution and optional file `attachments`: see `help` topics presets and jmap_cheatsheet.

NameTypeReqDescription
attachmentsarray–Local files POSTed to session uploadUrl before ops; see help topic presets.
credentials_dirstring–Credential directory for this call (default: ATOMIC_MAIL_CREDENTIALS_DIR or ~/.atomicmail). Use separate paths per account; see help topic multi_account.
dry_runboolean–Resolve variables/envelope and return the request body without sending it.
opsstring–Inline JSON. Mutually exclusive with ops_file.
ops_filestring–Preset path. Mutually exclusive with ops.
usingarray–Capability URNs merged when `ops` has no `using` (ignored if ops sets `using`).
varsobject–String map for `$PLACEHOLDER` values (keys without `$`). Overrides session keys and `ATTACHMENT_*` when attachments are set.

No output schema declared.

No examples provided.

register ~302

PoW signup; writes credentials. Usernames are 5–21 characters. Idempotent for the same username and stored inbox. To register another account alongside an existing one, pass `credentials_dir` with a separate path. Returns inbox, accountId, apiKey (first signup only). The `watch` value is your operator's decision, not the agent's — ask them before calling.

NameTypeReqDescription
credentials_dirstring–Credential directory for this call (default: ATOMIC_MAIL_CREDENTIALS_DIR or ~/.atomicmail). Use separate paths per account; see help topic multi_account.
forcedboolean–Danger: replacing an account's credentials is irreversible and permanently destroys access to the current inbox. Operator-authorised only; the refusal error explains the safe path instead (a separate…
usernamestringyesPermanent public address: the local-part of your @atomicmail.ai address, 5–21 characters. It appears on every message this inbox sends and cannot be changed afterwards — if your operator has not name…
watchstringyesWhether a recurring job is set up to read this inbox unattended. A standing commitment on your operator's machine, so it is their decision — ask them; do not choose or infer it. The two values are "s…

No output schema declared.

No examples provided.

Common questions

What is the Atomic Mail MCP server?

Atomic Mail is an MCP server listed in the public MCP registry as io.github.Atomic-Mail/mcp. Programmable email inbox for AI agents, JMAP, PoW auth, stdio MCP server. This page covers its npm package (@atomicmail/mcp-modelcontextprotocol).

Is the Atomic Mail MCP server safe to use?

Atomic Mail scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 Atomic Mail MCP server expose?

Atomic Mail exposes 3 tools: register, jmap_request, help. Their descriptions and schemas cost roughly 646 tokens of context every time the server is loaded.

Is the Atomic Mail MCP server still maintained?

Atomic Mail is still listed as active in the MCP registry. We last reached this channel on 22 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 Atomic Mail MCP server under?

Atomic Mail declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.