# EmptyInbox (npm · emptyinbox-mcp)

Zero-config disposable email inboxes for AI agents: create, read mail, await verify codes.

- Trust score: 71/100 (medium)
- Change this week: +33
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `emptyinbox-mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/cnohall-emptyinbox/emptyinbox-mcp.md), [page](https://verifymcp.io/servers/cnohall-emptyinbox/emptyinbox-mcp)

## Channel facts

- Registry: `npm`
- Package: `emptyinbox-mcp`
- Version: `1.3.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

## Install

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

### Claude

```bash
claude mcp add cnohall-emptyinbox -- npx -y emptyinbox-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cnohall-emptyinbox": {
      "command": "npx",
      "args": [
        "-y",
        "emptyinbox-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cnohall-emptyinbox": {
      "command": "npx",
      "args": [
        "-y",
        "emptyinbox-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cnohall-emptyinbox -- npx -y emptyinbox-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cnohall-emptyinbox": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "emptyinbox-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cnohall-emptyinbox --command npx --arg -y --arg emptyinbox-mcp
```

### Hermes

```yaml
mcp_servers:
  cnohall-emptyinbox:
    command: "npx"
    args: ["-y", "emptyinbox-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cnohall-emptyinbox": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "emptyinbox-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cnohall-emptyinbox -t stdio -c npx -a -y emptyinbox-mcp
```

### Other

```json
{
  "mcpServers": {
    "cnohall-emptyinbox": {
      "command": "npx",
      "args": [
        "-y",
        "emptyinbox-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-15 (score 71, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 56, +18)

- [security regression] Malware scan: pass → unverified
- [security improvement] 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.
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] 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

### 2026-09-13 (score 38, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-11 (score 23)

First indexed and scored.

## MCP tools (10)

### `register_account` (~98 tokens)

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.

Input parameters:

- `username` (string): Optional username (3-32 chars, letters/numbers/hyphens/underscores). Omit to have one allocated.

### `get_quota` (~34 tokens)

Check how many inbox credits remain on this account. When credits are low, the result says how to buy more with Bitcoin.

### `create_inbox` (~32 tokens)

Create a new disposable email inbox. Returns the email address. Use this before triggering any signup or email verification flow.

### `list_inboxes` (~19 tokens)

List all disposable email inboxes on this account.

### `list_messages` (~99 tokens)

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.

Input parameters:

- `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

### `get_message` (~124 tokens)

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.

Input parameters:

- `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, required): Message ID from list_messages

### `wait_for_message` (~145 tokens)

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.

Input parameters:

- `inbox` (string, required): 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)

### `buy_quota` (~183 tokens)

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.

Input parameters:

- `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…

### `list_bundles` (~37 tokens)

List the inbox credit bundles for sale and their USD prices, paid in Bitcoin. Show these to the user before calling buy_quota.

### `check_payment` (~110 tokens)

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.

Input parameters:

- `address` (string, required): 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)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cnohall-emptyinbox/emptyinbox-mcp#diagnostics

## Score history

- 2026-09-20: 71
- 2026-09-19: 71
- 2026-09-18: 71
- 2026-09-17: 71
- 2026-09-16: 71
- 2026-09-15: 71
- 2026-09-14: 56
- 2026-09-13: 38
- 2026-09-12: 23
- 2026-09-11: 23

## Common questions

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

## Links

- npm package: https://www.npmjs.com/package/emptyinbox-mcp
- Socket report: https://socket.dev/npm/package/emptyinbox-mcp
- Repository: https://github.com/blockonomics/emptyinbox-me
- Changelog RSS feed: https://verifymcp.io/servers/cnohall-emptyinbox/emptyinbox-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/cnohall-emptyinbox/emptyinbox-mcp.json
- HTML version of this page: https://verifymcp.io/servers/cnohall-emptyinbox/emptyinbox-mcp