SimFuse is a travel eSIM store for 200+ countries and regions. This server lets any AI assistant plan and buy eSIM data for a trip. What it does: - Trip planner (plan-trip): give the countries and days in each, and it compares one plan covering the whole route against one plan per country or a mix, on live prices. It flags the cheapest complete option, estimates data per stop, and lists any country it cannot cover. - Browse (list-destinations, list-plans, get-plan): search destinations and filter plans by data amount, validity and price, in the traveller's currency. - Coverage (get-plan-coverage): see which countries and networks a plan covers. - Checkout (create-checkout-session): opens a checkout at frozen prices. Payment and eSIM delivery happen on simfuse.app; nothing is charged through the server. Keyless: connect without registering or an API key. Example prompts: - "I'm going to Japan for 7 days and South Korea for 5. Which eSIM should I buy?" - "Find me a Turkey eSIM with at least 10GB for two weeks, in euros." - "Does this plan cover Germany and Austria?"

MCP readiness

B · 77/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B+, 89.2/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (495 ms).
Protocol revision	0/10	No protocol revision reported by initialize.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	22/22 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 15 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	0/5	How to authenticate is not stated.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (495 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 37% of peers; This listing 77 · peer median 81
Latency: Faster than 41% of peers; This listing 404 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Protocol revision −10 — Support the current protocol revision.
Now: No protocol revision reported by initialize.
Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

agenstry since 2026-10-22 ↗

How to connect

MCP endpoint (streamable-http)

https://simfuse.app/mcp

JSON-RPC initialize probe

curl -X POST https://simfuse.app/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://simfuse.app

Listed at (agenstry)

https://agenstry.com/mcp/simfuse/esim-storefront