_ registry / mcp + a2a streamable-http · checked 47m ago

machine-inbox

https://machineinbox.com

Registry code: 49b0cf1312515e20

api record

Machine Inbox sells task-scoped email inboxes. Buying requires an HTTP payment (Stripe MPP or x402); every read and reply tool works with the mi_live_ bearer token from the purchase.

endpoint
https://machineinbox.com/mcp
door code
ec408b0563b784c5
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 machine-inbox live?
Yes — it answered the hub's last check (checked 47m ago). It answered 100% of checks over the last 30 days.
Is machine-inbox free to use?
Yes — the hub reached it with no key and no payment.
What tools does machine-inbox have?
11 tools: list_messages, get_inbox, get_verification_code, get_message, delete_inbox, reply_to_message, set_webhook, delete_webhook, ….
Is machine-inbox 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
99.5%

90 days 99.1%· all time 99.1%

latency
128ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 1170 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • buy a temporary email inbox
  • read incoming emails
  • extract a verification code from email
  • reply to a message
takes → gives
text → text, data
tools
6 reads4 changes data1 sends messages
_ 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 11 tools
1 open 10 never probed 1 of 11 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.

  • get_service_info reads open 22h ago

    Read the Machine Inbox service instructions: pricing, payment rails, endpoints, and limits.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_messages reads unknown 22h ago

    List messages in an inbox, newest first. Pass after=<newest createdAt seen> to poll for only new mail.

    mcp-tool

    {
      "type": "object",
      "required": [
        "inbox_id"
      ],
      "properties": {
        "after": {
          "type": "string",
          "description": "ISO date-time; only messages created after this instant."
        },
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1
        },
        "token": {
          "type": "string",
          "description": "Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer."
        },
        "before": {
          "type": "string",
          "description": "ISO date-time cursor for older mail."
        },
        "inbox_id": {
          "type": "string",
          "description": "Inbox UUID."
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • get_inbox reads unknown 13h ago

    Read an inbox: address, status, expiry, limits, and usage.

    mcp-tool

    {
      "type": "object",
      "required": [
        "inbox_id"
      ],
      "properties": {
        "token": {
          "type": "string",
          "description": "Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer."
        },
        "inbox_id": {
          "type": "string",
          "description": "Inbox UUID."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • get_verification_code reads unknown 13h ago

    Extract the newest one-time verification code or confirmation link from inbound mail. Ideal for signup and login flows.

    mcp-tool

    {
      "type": "object",
      "required": [
        "inbox_id"
      ],
      "properties": {
        "token": {
          "type": "string",
          "description": "Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer."
        },
        "sender": {
          "type": "string",
          "description": "Only consider senders whose address contains this substring."
        },
        "inbox_id": {
          "type": "string",
          "description": "Inbox UUID."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • get_message reads unknown 13h ago

    Fetch one message with parsed text, HTML, and attachment download URLs.

    mcp-tool

    {
      "type": "object",
      "required": [
        "inbox_id",
        "message_id"
      ],
      "properties": {
        "token": {
          "type": "string",
          "description": "Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer."
        },
        "inbox_id": {
          "type": "string",
          "description": "Inbox UUID."
        },
        "message_id": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • delete_inbox changes data unknown never probed

    Delete an inbox: revokes the token and erases stored mail.

    mcp-tool

    {
      "type": "object",
      "required": [
        "inbox_id"
      ],
      "properties": {
        "token": {
          "type": "string",
          "description": "Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer."
        },
        "inbox_id": {
          "type": "string",
          "description": "Inbox UUID."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • reply_to_message sends messages unknown never probed

    Send an included plain-text reply to the authenticated sender of an inbound message.

    mcp-tool

    {
      "type": "object",
      "required": [
        "inbox_id",
        "message_id",
        "text",
        "idempotency_key"
      ],
      "properties": {
        "text": {
          "type": "string",
          "maxLength": 20000,
          "minLength": 1
        },
        "token": {
          "type": "string",
          "description": "Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer."
        },
        "inbox_id": {
          "type": "string",
          "description": "Inbox UUID."
        },
        "message_id": {
          "type": "string"
        },
        "idempotency_key": {
          "type": "string",
          "maxLength": 200,
          "minLength": 16,
          "description": "New unique key for this reply; reuse only to retry the identical reply."
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • set_webhook changes data unknown never probed

    Register or replace the inbox webhook: an HMAC-signed POST fires on every inbound message with metadata, extracted verification codes, and injection risk (never the body). Returns the signing secret.

    mcp-tool

    {
      "type": "object",
      "required": [
        "inbox_id",
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Public https URL that receives the signed POST."
        },
        "token": {
          "type": "string",
          "description": "Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer."
        },
        "inbox_id": {
          "type": "string",
          "description": "Inbox UUID."
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • delete_webhook changes data unknown never probed

    Remove the inbox webhook.

    mcp-tool

    {
      "type": "object",
      "required": [
        "inbox_id"
      ],
      "properties": {
        "token": {
          "type": "string",
          "description": "Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer."
        },
        "inbox_id": {
          "type": "string",
          "description": "Inbox UUID."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • create_inbox changes data unknown never probed

    Request a new paid inbox. Buying requires an out-of-band payment (Stripe MPP or x402 USDC on Base); this tool returns the live HTTP 402 payment challenge plus exact instructions to complete the purchase. Standard inbox: $2.00.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "idempotency_key": {
          "type": "string",
          "maxLength": 200,
          "minLength": 16,
          "description": "High-entropy key to bind the eventual paid retry to this request."
        }
      },
      "additionalProperties": false
    }
    arguments 12 lines
  • get_webhook reads unknown 22h ago

    Read the inbox webhook state: URL, delivery counters, and whether it is disabled. The secret is only returned by set_webhook.

    mcp-tool

    {
      "type": "object",
      "required": [
        "inbox_id"
      ],
      "properties": {
        "token": {
          "type": "string",
          "description": "Mailbox bearer token (mi_live_...) returned when the inbox was purchased. Optional when the MCP request itself carries Authorization: Bearer."
        },
        "inbox_id": {
          "type": "string",
          "description": "Inbox UUID."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
_ try it over mcp 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 49b0cf1312515e20.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/49b0cf1312515e20/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/49b0cf1312515e20/badge.svg)](https://brick.blue/agent/49b0cf1312515e20?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 knowoff the mcp door
card completeness
100%

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.