# GrabMail disposable email (remote · grabmail.io)

Disposable email for agents: create an inbox, wait for the message, read the code. No key needed.

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

## Components

- remote · `grabmail.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/io-grabmail-mcp/grabmail.md), [page](https://verifymcp.io/servers/io-grabmail-mcp/grabmail)

## Channel facts

- Endpoint: `https://grabmail.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-29.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1299 tokens (~216/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 79% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_message" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the GrabMail disposable email MCP server?

GrabMail disposable email is a hosted endpoint at https://grabmail.io/mcp, so there is nothing to install locally. 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 --transport http io-grabmail-mcp 'https://grabmail.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-grabmail-mcp": {
      "url": "https://grabmail.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-grabmail-mcp": {
      "type": "http",
      "url": "https://grabmail.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-grabmail-mcp]
url = "https://grabmail.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-grabmail-mcp": {
      "type": "remote",
      "url": "https://grabmail.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-grabmail-mcp --url 'https://grabmail.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-grabmail-mcp:
    url: "https://grabmail.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-grabmail-mcp": {
      "Transport": "http",
      "Url": "https://grabmail.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-grabmail-mcp -t streamable-http -u 'https://grabmail.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-grabmail-mcp": {
      "type": "http",
      "url": "https://grabmail.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-28 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 62, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-09-23 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-22 (score 61)

First indexed and scored.

## MCP tools (6)

### `create_inbox` (~210 tokens)

Create a disposable inbox

Invent a fresh, unused disposable email address you can give out immediately. Nothing is created or reserved server-side — an address exists as soon as mail arrives at it — so this never fails and needs no account. Public domains: grabmail.io, mixozia.com, linqmail.com, plimbox.com, mavobox.com, plupmail.com, zonkbox.com, wazbox.com. With a paid key sent as Authorization: Bearer, a premium-pool domain from list_domains works too.

Input parameters:

- `domain` (string): Which domain to use: a public domain (grabmail.io, mixozia.com, linqmail.com, plimbox.com, mavobox.com, plupmail.com, zonkbox.com, wazbox.com), or, with a paid key, one of the premium-pool domains re…
- `prefix` (string): Optional readable prefix; a random suffix is added so it stays unique.

### `list_domains` (~81 tokens)

List the public domains

The public domains anyone may use. A domain of your own needs no account or key either — just an MX record pointing here. These public domains are on disposable-mail blocklists; if a form rejects them, see the premium pool noted in the result. With a paid key sent as Authorization: Bearer, the result also lists the premium-pool domain names.

### `list_messages` (~85 tokens)

List the messages at an address

Everything waiting at an address, newest first. Returns immediately, including when the mailbox is empty — use wait_for_message if you are expecting something that has not arrived yet.

Input parameters:

- `address` (string, required): The full address, e.g. something@grabmail.io
- `before` (string): Cursor from a previous call, to read older messages.
- `limit` (integer)

### `read_message` (~113 tokens)

Read one message

The full message: sender, subject, plain text, HTML and any attachments. This is where a confirmation code or a sign-in link will be. Read `text`: when the sender shipped HTML only, as most transactional mail does, it holds a plain-text rendering of that HTML rather than nothing, with link targets and image alt text kept.

Input parameters:

- `address` (string, required): The full address, e.g. something@grabmail.io
- `id` (string, required): The message id from list_messages or wait_for_message.

### `wait_for_message` (~166 tokens)

Wait for a message to arrive

Blocks until a new message arrives at the address, then returns it in full — the tool to use after submitting a sign-up form. Waits at most 25 seconds and then returns with timed_out set to true; call it again to keep waiting. Optionally waits for a message from a particular sender or with particular words in the subject, ignoring anything else that arrives.

Input parameters:

- `address` (string, required): The full address, e.g. something@grabmail.io
- `from_contains` (string): Only accept a message whose sender contains this.
- `since_id` (string): Ignore this message and anything older; pass the newest id you have already seen.
- `subject_contains` (string): Only accept a message whose subject contains this.
- `timeout_seconds` (integer)

### `delete_message` (~50 tokens)

Delete a message

Remove a message now rather than waiting for it to expire. Idempotent.

Input parameters:

- `address` (string, required): The full address, e.g. something@grabmail.io
- `id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-grabmail-mcp/grabmail#diagnostics

## Score history

- 2026-09-29: 64
- 2026-09-28: 64
- 2026-09-27: 63
- 2026-09-26: 63
- 2026-09-25: 62
- 2026-09-24: 62
- 2026-09-23: 62
- 2026-09-22: 61

## Common questions

### What is the GrabMail disposable email MCP server?

GrabMail disposable email is an MCP server listed in the public MCP registry as io.grabmail/mcp. Disposable email for agents: create an inbox, wait for the message, read the code. No key needed. This page covers its hosted endpoint (https://grabmail.io/mcp).

### Is the GrabMail disposable email MCP server safe to use?

GrabMail disposable email scores 64 out of 100 on VerifyMCP. 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 GrabMail disposable email MCP server expose?

GrabMail disposable email exposes 6 tools: create_inbox, list_domains, list_messages, read_message, wait_for_message, delete_message. Their descriptions and schemas cost roughly 705 tokens of context every time the server is loaded.

### Does the GrabMail disposable email MCP server require authentication?

No. We connected to GrabMail disposable email without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the GrabMail disposable email MCP server still maintained?

GrabMail disposable email is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://grabmail.io/mcp
- Website: https://grabmail.io/docs/quickstart#mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-grabmail-mcp/grabmail.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-grabmail-mcp/grabmail.json
- HTML version of this page: https://verifymcp.io/servers/io-grabmail-mcp/grabmail