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

esimker

https://esimker.com

Registry code: 5d78d4f4954893a0

api record

esimker sells prepaid travel data eSIMs: data only, no phone numbers, no SMS, no voice. Prices are USD strings, from $1.00. No account is needed: an order is addressed by a secret token, a wallet by a secret code.

Two ways to buy:

endpoint
https://esimker.com/api/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 esimker live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is esimker free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does esimker have?
12 tools: get_payment_methods, create_checkout, get_order, create_deposit, get_plans, purchase_esim, create_wallet, get_deposit, ….
Is esimker 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
149ms

last good check

priced tools
0

of 12 tools

_ answered our checks, 90 days 296 checks · signed record
  • unknown → live
_ what it is for
used for
  • search travel esim destinations
  • get esim data plans
  • buy a travel esim
  • check esim data usage
  • top up a prepaid wallet
takes → gives
text, payments → data
tools
8 reads3 changes data1 moves money
_ 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 12 tools
1 open1 auth-required 10 never probed 2 of 12 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.

  • search_destinations reads open 15h ago

    Destinations on sale. `query` matches the name in any of 18 languages, the slug or the ISO code; empty lists everything. Each item: dest_code, slug, name, min_retail (USD, the cheapest fixed plan), unlimited_from (USD per day of a Daily Unlimited pass, or null), plan_count. Continue with get_plans(slug).

    mcp-tool

    {
      "type": "object",
      "title": "search_destinationsArguments",
      "properties": {
        "query": {
          "type": "string",
          "title": "Query",
          "default": ""
        }
      }
    }
    arguments 11 lines
  • get_wallet reads auth-required 15h ago

    The wallet behind the code: ref (a public handle for support), balance_usd, cashback_percent, the deposit rules that apply to it now (min_usd, max_usd, first, bonus tiers), the last 50 transactions, orders (with their tokens — the wallet is where a buyer's order links are kept) and deposits. Needs the wallet code.

    mcp-tool

    {
      "type": "object",
      "title": "get_walletArguments",
      "properties": {}
    }
    arguments 5 lines
  • get_payment_methods reads unknown never probed

    Checkout methods open right now: "crypto" (a hosted invoice: BTC, ETH, TRX, USDT), "card", and "wallet" (a prepaid balance, see create_wallet). `gateways` names the providers behind each method; a checkout that does not ask for one by name goes to the first, which is what these tools do.

    mcp-tool

    {
      "type": "object",
      "title": "get_payment_methodsArguments",
      "properties": {}
    }
    arguments 5 lines
  • create_checkout changes data unknown never probed

    Create an order for a person to pay. Returns token, checkout_url (the gateway's page: hand it to the person) and order_url (the order page in `lang`, with the QR code once paid: show it to the buyer only, the token is a secret). Confirm the plan and the price first: every call creates a new unpaid order, so do not retry while a checkout is open. `email` (optional) also gets the eSIM by mail. `period_num` (1–365) only for daily_unlimited plans. `topup_iccid` with a plan_id from list_topups tops up an existing eSIM. A 403 means the caller's jurisdiction is embargoed. To pay from a wallet use purchase_esim.

    mcp-tool

    {
      "type": "object",
      "title": "create_checkoutArguments",
      "required": [
        "plan_id"
      ],
      "properties": {
        "lang": {
          "type": "string",
          "title": "Lang",
          "default": "en"
        },
        "email": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Email",
          "default": null
        },
        "plan_id": {
          "type": "integer",
          "title": "Plan Id",
          "maximum": 2147483647,
          "minimum": 1
        },
        "period_num": {
          "anyOf": [
            {
              "type": "integer"
            },
            {
              "type": "null"
            }
          ],
          "title": "Period Num",
          "default": null
        },
        "topup_iccid": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Topup Iccid",
          "default": null
        },
        "payment_method": {
          "enum": [
            "crypto",
            "card"
          ],
          "type": "string",
          "title": "Payment Method",
          "default": "crypto"
        }
      }
    }
    arguments 65 lines
  • get_order reads unknown never probed

    An order by its token. status goes pending (unpaid) → paid → provisioning → ready; also expired, underpaid, failed_provisioning, gift_waiting, and payment_held — the payment processor's compliance check stopped the payment and holds the money: nothing is issued, the person must not pay again and should write to support. When ready, esim.activation_code is the LPA string (render it as a QR code), with iccid, smdp and matching_id. After payment poll every ~10 s; delivery usually takes under a minute.

    mcp-tool

    {
      "type": "object",
      "title": "get_orderArguments",
      "required": [
        "token"
      ],
      "properties": {
        "token": {
          "type": "string",
          "title": "Token"
        }
      }
    }
    arguments 13 lines
  • create_deposit changes data unknown never probed

    Open a top-up of the wallet and get what is needed to pay it. Floors: $10 for a wallet's first deposit, $1 after that; cap $1000 per deposit. Crypto deposits earn a bonus (+2% from $25, +3% from $50, +5% from $100, capped at $25); every purchase returns 3% cashback. With payment_method "crypto" pass a currency from: BTC, ETH, TRX, USDTTRC, USDTETH, USDTBSC — the answer then carries `pay`: the address, the exact amount in the coin (network fee included) and expires_at (about 15 minutes; after that open a new deposit). Send exactly `pay.amount` to `pay.address` on `pay.network`, then poll get_deposit(token) until status is paid. checkout_url is the hosted pay page for a person; card deposits have only that. Needs the wallet code.

    mcp-tool

    {
      "type": "object",
      "title": "create_depositArguments",
      "required": [
        "amount_usd"
      ],
      "properties": {
        "lang": {
          "type": "string",
          "title": "Lang",
          "default": "en"
        },
        "currency": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Currency",
          "default": null
        },
        "amount_usd": {
          "anyOf": [
            {
              "type": "number"
            },
            {
              "type": "string"
            }
          ],
          "title": "Amount Usd"
        },
        "payment_method": {
          "enum": [
            "crypto",
            "card"
          ],
          "type": "string",
          "title": "Payment Method",
          "default": "crypto"
        }
      }
    }
    arguments 46 lines
  • get_plans reads unknown 11h ago

    The plans of one destination (slug from search_destinations). Each plan: id (the plan_id for an order), name, gb, days, retail (USD; per day when daily_unlimited is true), daily_unlimited, location_codes (the countries it covers), networks, speed, supports_topup. Also the published rating.

    mcp-tool

    {
      "type": "object",
      "title": "get_plansArguments",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "title": "Slug"
        }
      }
    }
    arguments 13 lines
  • purchase_esim moves money unknown never probed

    Charge the wallet and issue an eSIM, no checkout. `client_ref` (1–64 chars) is your own reference for this purchase and makes the call idempotent: a retry with the same value returns the existing order without a second charge, so reuse it after a timeout and never invent a new one for the same purchase. `period_num` (1–365, default 7) only for daily_unlimited plans; the charge is price × days. `topup_iccid` with a plan_id from list_topups tops up an eSIM. Returns the order (status paid) with order_url; poll get_order(token) for ready and the activation code. A 402 is a short balance: create_deposit first. A wallet pays for at most 50 orders in 24 hours (429 beyond that; a retry answered from client_ref does not count). Needs the wallet code.

    mcp-tool

    {
      "type": "object",
      "title": "purchase_esimArguments",
      "required": [
        "plan_id",
        "client_ref"
      ],
      "properties": {
        "lang": {
          "type": "string",
          "title": "Lang",
          "default": "en"
        },
        "email": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Email",
          "default": null
        },
        "plan_id": {
          "type": "integer",
          "title": "Plan Id",
          "maximum": 2147483647,
          "minimum": 1
        },
        "client_ref": {
          "type": "string",
          "title": "Client Ref"
        },
        "period_num": {
          "anyOf": [
            {
              "type": "integer"
            },
            {
              "type": "null"
            }
          ],
          "title": "Period Num",
          "default": null
        },
        "topup_iccid": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Topup Iccid",
          "default": null
        }
      }
    }
    arguments 61 lines
  • create_wallet changes data unknown never probed

    Mint a prepaid wallet with no account behind it and get its secret ONCE: `code` (32 hex characters) and the same secret as a 12-word `phrase`. Save the code before doing anything else and send it as `Authorization: Bearer <code>` on every wallet call; there is no recovery and no identity to prove. The balance is spent on eSIMs (retail price, cashback on every purchase) and never paid back out. accept_terms must be true (https://esimker.com/terms). Then create_deposit to fund it. Rate-limited and geo-blocked like checkout.

    mcp-tool

    {
      "type": "object",
      "title": "create_walletArguments",
      "required": [
        "accept_terms"
      ],
      "properties": {
        "accept_terms": {
          "type": "boolean",
          "title": "Accept Terms"
        }
      }
    }
    arguments 13 lines
  • get_deposit reads unknown never probed

    One deposit of the wallet by its token: status pending → paid (credited, bonus included) | underpaid (nothing credited yet, the rest can still arrive) | payment_held (the payment processor's compliance check stopped the payment and holds it: nothing is credited, do not pay again, the person should write to support) | expired. Poll every ~30 s after sending; crypto needs the network's confirmations. Needs the wallet code.

    mcp-tool

    {
      "type": "object",
      "title": "get_depositArguments",
      "required": [
        "token"
      ],
      "properties": {
        "token": {
          "type": "string",
          "title": "Token"
        }
      }
    }
    arguments 13 lines
  • get_usage reads unknown 15h ago

    Remaining data and status of an eSIM we issued.

    mcp-tool

    {
      "type": "object",
      "title": "get_usageArguments",
      "required": [
        "iccid"
      ],
      "properties": {
        "iccid": {
          "type": "string",
          "title": "Iccid"
        }
      }
    }
    arguments 13 lines
  • list_topups reads unknown 11h ago

    Top-up plans that fit an eSIM we issued: plan_id, name, gb, days, retail. Order one with create_checkout(plan_id, topup_iccid=iccid) or, from a wallet, purchase_esim(plan_id, client_ref, topup_iccid=iccid).

    mcp-tool

    {
      "type": "object",
      "title": "list_topupsArguments",
      "required": [
        "iccid"
      ],
      "properties": {
        "iccid": {
          "type": "string",
          "title": "Iccid"
        }
      }
    }
    arguments 13 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 5d78d4f4954893a0.

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