EmptyInbox
NPM · EMPTYINBOX-MCP · SCANNED SEP 20
Zero-config disposable email inboxes for AI agents: create, read mail, await verify codes.
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 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1106 tokens (~110/item across 10 items; 10 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
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.
How do I install the EmptyInbox MCP server?
EmptyInbox runs locally as an npm package, launched with npx -y emptyinbox-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 · emptyinbox-mcp
claude mcp add cnohall-emptyinbox -- npx -y emptyinbox-mcp
{
"mcpServers": {
"cnohall-emptyinbox": {
"command": "npx",
"args": [
"-y",
"emptyinbox-mcp"
]
}
}
} {
"servers": {
"cnohall-emptyinbox": {
"command": "npx",
"args": [
"-y",
"emptyinbox-mcp"
]
}
}
} codex mcp add cnohall-emptyinbox -- npx -y emptyinbox-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cnohall-emptyinbox": {
"type": "local",
"command": [
"npx",
"-y",
"emptyinbox-mcp"
],
"enabled": true
}
}
} openclaw mcp add cnohall-emptyinbox --command npx --arg -y --arg emptyinbox-mcp
mcp_servers:
cnohall-emptyinbox:
command: "npx"
args: ["-y", "emptyinbox-mcp"] {
"McpServers": {
"cnohall-emptyinbox": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"emptyinbox-mcp"
]
}
}
} assistant mcp add cnohall-emptyinbox -t stdio -c npx -a -y emptyinbox-mcp
{
"mcpServers": {
"cnohall-emptyinbox": {
"command": "npx",
"args": [
"-y",
"emptyinbox-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.
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 +18
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 1.2.1 → 1.3.0 functional
- 13 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 23
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 20 Sept 2026 · Analysed npm/emptyinbox-mcp@1.3.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 →
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 →
buy_quota ~183
Buy inbox credits with Bitcoin. Only call this after the user has chosen a bundle or amount. Returns a pay_url to give the user: a page with a QR code, the exact amount and a live payment status, which works with any Bitcoin wallet. Also returns the raw address, amount and BIP21 URI for paying directly. Credits are added as soon as the payment is seen on the network. Call check_payment once the user has paid.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | string | – | Bundle id from list_bundles (default: starter) |
| usd | integer | – | Spend a custom whole-dollar amount instead of a bundle, from 1 to 100. Priced at the best bundle rate the amount qualifies for. The network fee the payer adds on top is the same whatever the size of… |
No output schema declared.
No examples provided.
check_payment ~110
Check whether a Bitcoin payment from buy_quota has landed. Pass wait_seconds (around 120) once the user says they have paid, to wait for the credits in one call. Credit usually arrives within seconds of broadcast, well before confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Payment address returned by buy_quota |
| poll_interval_seconds | number | – | Seconds between checks (default: 5) |
| wait_seconds | number | – | Seconds to keep polling for credit (default: 0, check once) |
No output schema declared.
No examples provided.
create_inbox ~32
Create a new disposable email inbox. Returns the email address. Use this before triggering any signup or email verification flow.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_message ~124
Get one email message by ID. Returns the parsed message: extracted code, action_url, every link with its anchor text, and the body as plain text. Set format='text' for a flat rendering to read directly, or include_html=true only if the raw HTML is genuinely needed.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | json (structured) or text (flat, prompt-ready) |
| include_html | boolean | – | Include the raw html_body in json output (default: false — it is large and rarely needed) |
| message_id | string | yes | Message ID from list_messages |
No output schema declared.
No examples provided.
get_quota ~34
Check how many inbox credits remain on this account. When credits are low, the result says how to buy more with Bitcoin.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_bundles ~37
List the inbox credit bundles for sale and their USD prices, paid in Bitcoin. Show these to the user before calling buy_quota.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_inboxes ~19
List all disposable email inboxes on this account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_messages ~99
List received email messages, newest first, already parsed: each entry carries the extracted one-time code, the link to open, and a text preview — no HTML parsing needed. Filter by inbox and use limit to keep responses small.
| Name | Type | Req | Description |
|---|---|---|---|
| inbox | string | – | Filter to a specific inbox email address |
| limit | number | – | Max messages to return (default: 10) |
| since | number | – | Unix seconds — only messages received after this |
No output schema declared.
No examples provided.
register_account ~98
Register a new EmptyInbox account and get an API key. Use this only if there is no account configured yet, or if authentication is failing. Prefer reusing an existing key: repeatedly registering from one network reduces the free credits each new account receives. Saves the key locally for future sessions.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | – | Optional username (3-32 chars, letters/numbers/hyphens/underscores). Omit to have one allocated. |
No output schema declared.
No examples provided.
wait_for_message ~145
Poll an inbox until a new message arrives. Use after triggering an email verification, OTP, or signup confirmation. Returns the parsed message — including the extracted code and the link to open — as soon as it lands, or a timeout result.
| Name | Type | Req | Description |
|---|---|---|---|
| inbox | string | yes | Inbox email address to watch |
| poll_interval_seconds | number | – | Seconds between checks (default: 5) |
| require_code | boolean | – | Keep waiting until a message carries an extracted code or action link |
| subject_contains | string | – | Only match messages whose subject contains this text (case-insensitive) |
| timeout_seconds | number | – | Seconds to wait before giving up (default: 120) |
No output schema declared.
No examples provided.
What is the EmptyInbox MCP server?
EmptyInbox is an MCP server listed in the public MCP registry as io.github.cnohall/emptyinbox. Zero-config disposable email inboxes for AI agents: create, read mail, await verify codes. This page covers its npm package (emptyinbox-mcp).
Is the EmptyInbox MCP server safe to use?
EmptyInbox scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 EmptyInbox MCP server expose?
EmptyInbox exposes 10 tools: register_account, get_quota, create_inbox, list_inboxes, list_messages, and 5 more. Their descriptions and schemas cost roughly 881 tokens of context every time the server is loaded.
Is the EmptyInbox MCP server still maintained?
EmptyInbox is still listed as active in the MCP registry. We last reached this channel on 20 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 EmptyInbox MCP server under?
EmptyInbox declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.