mcp-registry/io.grabmail/mcp · v1.0.0
As of 2026-10-27 03:20 UTC, the Grabmail MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 8 minutes.
Disposable email for agents: create an inbox, wait for the message, read the code. No key needed.
Point your MCP client at this streamable-http endpoint: https://grabmail.io/mcp
6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
3 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.grabmail%2Fmcp/fixes
{
"name": "create_inbox",
"description": "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. With a paid key sent as Authorization: Bearer, a premium-pool domain from list_domains works too.",
"inputSchema": {
"type": "object",
"properties": {
"domain": {
"type": "string",
"description": "Which domain to use: a public domain (grabmail.io, mixozia.com, linqmail.com), or, with a paid key, one of the premium-pool domains returned by list_domains. Defaults to grabmail.io."
},
"prefix": {
"type": "string",
"maxLength": 40,
"description": "Optional readable prefix; a random suffix is added so it stays unique."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Create a disposable inbox"
}{
"name": "delete_message",
"description": "Remove a message now rather than waiting for it to expire. Idempotent.",
"inputSchema": {
"type": "object",
"required": [
"address",
"id"
],
"properties": {
"id": {
"type": "string"
},
"address": {
"type": "string",
"description": "The full address, e.g. [email protected]"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
},
"title": "Delete a message"
}{
"name": "list_domains",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "List the public domains"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.grabmail/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.grabmail/mcp"}) over MCP.
wait_for_message ~278 tokenscreate_inbox ~234 tokensread_message ~181 tokenslist_messages ~160 tokenslist_domains ~128 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.grabmail%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.grabmail%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.grabmail%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.grabmail%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.grabmail%2Fmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f3f3e079495a7673…, first seen 2026-10-17, included at leaf 1310 of 77,063. Version history · verify what your client received.
Compare: most reliable email servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 03:20 UTC, the Grabmail MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 8 minutes.
Grabmail MCP server advertises 6 tools, including create_inbox, delete_message, list_domains, list_messages, read_message.
Point your MCP client at this streamable-http endpoint: https://grabmail.io/mcp
Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.