Official MCP server for NexaEsim. Enables AI agents to search global travel eSIM data plans, manage carts, and generate secure checkout links. # NexaEsim MCP Commerce Server NexaEsim is a public retail MCP server that allows AI shopping agents to search, select, and build carts for global travel eSIM data plans across 150+ countries and regions. ### Key Capabilities - **Destination Lookup (`search_countries`)**: Resolve destination names or ISO 3166-1 alpha-2/3 country codes. - **eSIM Plan Search (`search_esim`)**: Search real-time retail eSIM packages filtered by country, duration (days), and data allowance (GB or unlimited). - **Cart Management (`create_cart`, `add_to_cart`, `get_cart`, `set_cart_item_quantity`)**: Build and update server-side shopping carts programmatically. - **Secure Checkout (`generate_checkout_url`)**: Generate short-lived, secure payment links directing customers to complete checkout on NexaEsim. ### Key Highlights - **Public & Rate-Limited**: No authentication or API keys required. - **Currency & Pricing**: Transparent retail prices in USD. - **Zero Payment Friction**: AI agents never collect or transmit payment credentials—all financial transactions happen directly on NexaEsim's secure checkout page. ### Endpoints - **Primary Transport**: `https://nexaesim.com/mcp` - **Legacy SSE Endpoint**: `https://nexaesim.com/mcp/sse` - **Machine-readable Manifest**: `https://nexaesim.com/.well-known/mcp.json`
MCP readiness
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 C+, 70.0/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 | 22/25 | Endpoint answers the MCP initialize handshake (9324 ms); near timeout response -3. |
| Protocol revision | 6/10 | Speaks MCP 2025-06-18, 2 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 | 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 | 2/5 | Declares credential scheme: smithery_api_key. |
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 55% of peers
- This listing 82 · peer median 81
- Latency
- Faster than 5% of peers
- This listing 1,828 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- 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.
- Protocol revision −4
— Support the current protocol revision.
Now: Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
- Live MCP endpoint −3
— Answer initialize and tools/list at the declared endpoint.
Now: Endpoint answers the MCP initialize handshake (9324 ms); near timeout response -3.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/dongnt/nexaesim/mcpcurl -X POST https://server.smithery.ai/dongnt/nexaesim/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'