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.

GrabMail disposable email

REMOTE · GRABMAIL.IO · SCANNED SEP 29

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

Available components

+3 this week 64 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 79% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 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. See how to fix → Fail
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

remote · grabmail.io

# add to Claude Code
claude mcp add --transport http io-grabmail-mcp 'https://grabmail.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-grabmail-mcp": {
      "url": "https://grabmail.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-grabmail-mcp": {
      "type": "http",
      "url": "https://grabmail.io/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add io-grabmail-mcp --url 'https://grabmail.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-grabmail-mcp:
    url: "https://grabmail.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-grabmail-mcp": {
      "Transport": "http",
      "Url": "https://grabmail.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-grabmail-mcp -t streamable-http -u 'https://grabmail.io/mcp'
// mcp.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 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.

  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 +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.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 23 Sept 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 22 Sept 26 61

    First indexed and scored.

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 29 Sept 2026 · Probed https://grabmail.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=grabmail.io CN=WE1,O=Google Trust Services,C=US 4 Aug 2026 2 Nov 2026 ECDSA 256 ECDSA-SHA256 9a5d6271388b2886139df9373af396e9
SANs: grabmail.io, *.grabmail.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of grabmail.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
grabmail.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000
content-security-policy default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; img-src 'self' data:; style-src 'self'; script-src 'self' https://challenges.cloudflare.com; font-src 'self'; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com; child-src 'self' https://challenges.cloudflare.com
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://grabmail.io/mcp Verified 200
http (plaintext) http://grabmail.io/mcp HTTPS enforced 301 https://grabmail.io/mcp
MCP tools · 6 exposed · ~705 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
create_inbox ~210

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.

NameTypeReqDescription
domainstring–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…
prefixstring–Optional readable prefix; a random suffix is added so it stays unique.

No output schema declared.

No examples provided.

delete_message ~50

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

NameTypeReqDescription
addressstringyesThe full address, e.g. something@grabmail.io
idstringyes–

No output schema declared.

No examples provided.

list_domains ~81

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_messages ~85

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.

NameTypeReqDescription
addressstringyesThe full address, e.g. something@grabmail.io
beforestring–Cursor from a previous call, to read older messages.
limitinteger––

No output schema declared.

No examples provided.

read_message ~113

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.

NameTypeReqDescription
addressstringyesThe full address, e.g. something@grabmail.io
idstringyesThe message id from list_messages or wait_for_message.

No output schema declared.

No examples provided.

wait_for_message ~166

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.

NameTypeReqDescription
addressstringyesThe full address, e.g. something@grabmail.io
from_containsstring–Only accept a message whose sender contains this.
since_idstring–Ignore this message and anything older; pass the newest id you have already seen.
subject_containsstring–Only accept a message whose subject contains this.
timeout_secondsinteger––

No output schema declared.

No examples provided.

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.