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

inbox-esim

https://inboxesim.com

Registry code: ba51ba8e4704477a

api record

Inbox eSIM sells prepaid, data-only travel eSIMs for 200+ countries and regions. Prices are in USD. Use find_esim_plans with the place the customer travels to, pick a plan with them, then buy_esim with the plan_id and the customer's email. buy_esim returns a payment link: POST to it, answer the HTTP 402 Machine Payments Protocol challenge with a Stripe shared payment token, and retry. The QR code and a one-tap install link are emailed to the customer within about a minute. No app and no account.

endpoint
https://inboxesim.com/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 inbox-esim live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is inbox-esim free to use?
Yes — the hub reached it with no key and no payment.
What tools does inbox-esim have?
2 tools: buy_esim, find_esim_plans.
Is inbox-esim 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
479ms

last good check

priced tools
0

of 2 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 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.

  • buy_esim unknown never probed

    Starts the purchase of one eSIM plan for the customer and returns a payment link. Pay it with the Machine Payments Protocol (HTTP 402, Stripe shared payment token) to complete the order. Before calling, confirm the plan, the price and the email with the customer, and get their agreement to the terms: By buying, the customer asks for the eSIM to be sent at once and accepts the terms (https://inboxesim.com/terms): the 14-day right to withdraw ends once the eSIM is installed. An eSIM that was never installed or used can be refunded within 30 days from its order page, less the payment fee (in full within 14 days in the EU and UK).

    mcp-tool

    {
      "type": "object",
      "required": [
        "plan_id",
        "customer_email",
        "customer_agreed_to_terms"
      ],
      "properties": {
        "plan_id": {
          "type": "string",
          "description": "A plan_id from find_esim_plans, e.g. 'japan-5gb-30d'."
        },
        "customer_email": {
          "type": "string",
          "description": "Where the QR code and install link are sent."
        },
        "customer_agreed_to_terms": {
          "type": "boolean",
          "description": "true only if the customer accepted the terms quoted in this tool's description."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • find_esim_plans unknown 2h ago

    Lists Inbox eSIM data plans for a destination (country, city, region such as Europe, or 'global'), cheapest first, with plan_id, data in GB, validity in days and price in USD. Data only, no phone number; works on unlocked eSIM phones.

    mcp-tool

    {
      "type": "object",
      "required": [
        "destination"
      ],
      "properties": {
        "min_days": {
          "type": "integer",
          "description": "Optional: only plans valid for at least this many days (the trip length)."
        },
        "destination": {
          "type": "string",
          "description": "Where the customer travels, e.g. 'Japan', 'USA', 'Europe', 'Bangkok'."
        },
        "min_data_gb": {
          "type": "number",
          "description": "Optional: only plans with at least this much data."
        }
      },
      "additionalProperties": false
    }
    arguments 21 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 ba51ba8e4704477a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ba51ba8e4704477a/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/ba51ba8e4704477a/badge.svg)](https://brick.blue/agent/ba51ba8e4704477a?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
60%

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.