esimsos
Registry code: 37e88ca3e215aa69
eSIM SOS sells travel data eSIMs (prices in RUB). Flow: search_destinations → list_plans (optionally compare_prices) → ask the user for email → create_order → give the user payment_url → order_status → install_instructions. Payment is always done by the human: give the user the payment link, never try to pay yourself and never ask for card details.
- endpoint
- https://esimsos.net/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 esimsos live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is esimsos free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does esimsos have?
- 6 tools: search_destinations, list_plans, order_status, install_instructions, create_order, compare_prices.
- Is esimsos 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.
90 days 100%· all time 100%
last good check
of 6 tools
- unknown → live
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.
through this hub
successful
what callers paid
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
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 unknown 1h ago
Find a travel destination (country) sold by eSIM SOS by name in English or Russian, or by ISO code. Returns country codes for list_plans.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "Country name or ISO code, e.g. \"Turkey\", \"Турция\", \"TR\"" } } }arguments 12 lineslist_plans unknown never probed
List eSIM data plans for a country with final prices in RUB (one price for every payment method). Local plans first, then regional ones.
{ "type": "object", "required": [ "country" ], "properties": { "days": { "type": "number", "description": "Optional: minimum validity in days" }, "min_gb": { "type": "number", "description": "Optional: minimum data in GB" }, "country": { "type": "string", "description": "ISO country code from search_destinations (e.g. TR) or the country name" } } }arguments 20 linesorder_status unknown never probed
Check the payment and delivery status of an order. Requires both order_id and the email used for the order.
{ "type": "object", "required": [ "order_id", "email" ], "properties": { "email": { "type": "string", "description": "The email used for the order" }, "order_id": { "type": "string", "description": "order_id returned by create_order" } } }arguments 17 linesinstall_instructions unknown 1h ago
After payment: link to the order page with the QR code and step-by-step eSIM install instructions for iPhone and Android. Requires order_id and email.
{ "type": "object", "required": [ "order_id", "email" ], "properties": { "email": { "type": "string", "description": "The email used for the order" }, "order_id": { "type": "string", "description": "order_id returned by create_order" } } }arguments 17 linescreate_order unknown never probed
Create an unpaid eSIM order and get a payment link. Payment is always done by the human: give the user the payment link, never try to pay yourself and never ask for card details. Ask the user for their email first: the eSIM QR code is sent there. Creates a real order, so call it only after the user picked the plan.
{ "type": "object", "required": [ "plan_id", "email" ], "properties": { "email": { "type": "string", "description": "The user's email for the receipt and the eSIM QR code" }, "plan_id": { "type": "string", "description": "plan_id from list_plans" }, "payment_method": { "enum": [ "sbp", "card", "card_foreign", "crypto_usdt", "crypto_ton" ], "type": "string", "description": "Optional: sbp (Russian fast payments), card (Russian bank card), card_foreign (Visa/Mastercard issued abroad), crypto_usdt, crypto_ton. Omit to use the shop default." } } }arguments 28 linescompare_prices unknown 1h ago
Compare eSIM prices of several providers for a country and data size using the open esimdar.com dataset (CC BY 4.0). Disclosure: esimdar.com is owned and run by eSIM SOS, the shop behind this server; eSIM SOS is listed as an ordinary row. Tell the user about this ownership and present the results neutrally.
{ "type": "object", "required": [ "country", "gb" ], "properties": { "gb": { "type": "number", "description": "Data size in GB, e.g. 5" }, "country": { "type": "string", "description": "ISO country code (e.g. TR) or the country name" } } }arguments 17 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id37e88ca3e215aa69.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/37e88ca3e215aa69/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/37e88ca3e215aa69?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.