Simsima Connectivity
https://mcp.simsima.io/mcpSearch, recommend & buy travel eSIM data plans for 190+ destinations via AI agents.
What we measured
Over the last 30 days we probed this MCP server 30 times on 30 days; it answered 30 (100%). Median response 665 ms, 95th percentile 837 ms.
When we called tools/list it returned 7 tools, including list_destinations, search_plans, get_plan, over MCP protocol revision 2025-11-25.
Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 17% and higher on readiness than 60%.
From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure
Tools (7)
As returned by the server's own tools/list when we called it.
- list_destinations
- List the destinations Simsima covers (countries, regions and global plans), with the entry price and product URL of each.
- search_plans
- Search the eSIM plans of a destination (country, region or global), cheapest first, with optional filters on price, data, validity and unlimited data.
- get_plan
- Get one eSIM plan by its sku, as returned by search_plans or recommend_plan.
- recommend_plan
- Recommend the best plan(s) for a trip to a destination, given its length in days and expected data usage (light, medium or heavy).
- create_checkout_link
- Return the URL of a plan's page on simsima.io, with the plan preselected, where the user can review and buy it. No order is placed and no payment is made by thi…
- check_coverage
- Answer "does this eSIM work in <country>" for a destination (country, region or global plan). Accepts a country name or ISO code.
- get_destination_info
- Coverage (ISO country codes), mobile operators, top-up availability and entry price for a destination.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here B+, 88.4/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 (802 ms). |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 7 tool(s) with descriptions. |
| Verified identity | 7/10 | Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time). |
| Freshness + modern flags | 0/5 | not seen in a source for over 30 days. |
| Auth declaration | 0/5 | How to authenticate is not stated. |
Compared with peers
Against 53,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.
- Readiness
- Higher than 60% of peers
- This listing 83 · peer median 81
- Latency
- Faster than 17% of peers
- This listing 802 ms · peer median 349 ms
Where it loses the most points, and how to win them back
- Freshness + modern flags −5
— Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
- Auth declaration −5
— State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.
- Verified identity −3
— Claim the listing and prove control of its domain.
Now: Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Listed in
Directories this entry was found in.
How to connect
https://mcp.simsima.io/mcpcurl -X POST https://mcp.simsima.io/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'