_ registry / mcp streamable-http · checked 1h ago

receivemail

https://receivemail.dev

Registry code: 464da0df3876ed20

api record

Disposable email inboxes for testing signup and verification-email flows. Call create_mailbox, give the address to the site under test, then wait_for_email with the returned address and secret. Plain-text bodies only; addresses expire (60 min free, 24 h with a paid key).

endpoint
https://receivemail.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is receivemail live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is receivemail free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does receivemail have?
3 tools: create_mailbox, wait_for_email, list_messages.
Is receivemail safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
52ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 auth-required 2 never probed 1 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_messages auth-required 1h ago

    List the last 50 emails received by a mailbox made with create_mailbox, newest first.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address",
    "secret"
  ],
  "properties": {
    "secret": {
      "type": "string",
      "description": "Secret returned by create_mailbox."
    },
    "address": {
      "type": "string",
      "description": "Address returned by create_mailbox."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • create_mailbox unknown never probed

    Create a disposable receivemail.dev email address that receives real mail. Returns address, expiresAt and secret; keep the secret to read the mailbox. Free without a key (up to 60 minutes); with a paid key on the MCP connection, up to 1440 minutes and an extracted otp field on messages.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "ttlMinutes": {
      "type": "integer",
      "maximum": 1440,
      "minimum": 1,
      "description": "Lifetime in minutes, default 15. Free tier caps at 60."
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • wait_for_email unknown never probed

    Wait up to 25 seconds for an email to a mailbox made with create_mailbox. Returns {timed_out:false, message:{from_address, subject, body_text, received_at}} or {timed_out:true}; call again on timeout. Pass `since` (ISO 8601) to ignore mail you've already seen.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address",
    "secret"
  ],
  "properties": {
    "since": {
      "type": "string",
      "description": "Optional ISO 8601 timestamp; only newer mail counts."
    },
    "secret": {
      "type": "string",
      "description": "Secret returned by create_mailbox."
    },
    "address": {
      "type": "string",
      "description": "Address returned by create_mailbox."
    },
    "timeout": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "Seconds to wait, default 25."
    }
  },
  "additionalProperties": false
}
    arguments 28 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 464da0df3876ed20.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/464da0df3876ed20/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/464da0df3876ed20/badge.svg)](https://brick.blue/agent/464da0df3876ed20?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.