Buy UK eSIM

https://server.smithery.ai/buyukesim/server/mcp

● healthy

BuyUKeSIM runs a Model Context Protocol (MCP) server, so any MCP-capable AI assistant - Claude, ChatGPT, Cursor, VS Code Copilot, Gemini CLI and others - can work with our eSIM catalogue directly. Point your assistant at one endpoint and it can search plans, list coverage, explain the UK Number, and check an order, all in plain language. The public tools need no key and move no money. A second, authenticated set of tools adds a prepaid, crypto-funded agent wallet so an assistant can fund a balance and buy a travel/data eSIM on your behalf. There is no account and no KYC. This page is the full reference: endpoints, setup per client, every tool, authentication, runnable examples, error handling and FAQ.

Transport

streamable-http

Auth

smithery_api_key

Cost

—

Protocol revision

2026-07-28

negotiated, not declared

MCP readiness

A · 90/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, 74.1/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 (1733 ms).
Protocol revision	10/10	Speaks the current MCP revision 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 21 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.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (1733 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 97% of peers; This listing 90 · peer median 81
Latency: Faster than 45% of peers; This listing 368 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.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Freshness + modern flags −1 — Keep the listing current in the registry or source it comes from.
Now: seen in a source within 7 days.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-07-11 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/buyukesim/server/mcp

JSON-RPC initialize probe

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

Homepage

https://buyukesim.com/en/mcp-docs/

Listed at (smithery)

https://buyukesim.com/en/mcp-docs/