Worldcitisim eSIM
NPM · @WORLDCITISIM/MCP-ESIM
Travel eSIMs for 193 countries. Stripe + Bitcoin checkout. QR by email in 30s. No API key.
Available components
Last scanned (1 hour ago)
Scores higher than 76% of npm servers
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 109 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 679 tokens (~169/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.93 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.93 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 −3
- Stability: pass → 0.77 functional
- 13 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@worldcitisim/mcp-esim@0.2.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
esim_check_order ~77
Poll an order's status. Returns `status: pending` while waiting for payment, `status: processing` or `completed` once paid, with `activation` data (ICCID, QR URL, install instructions).
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | number | yes | – |
| order_token | string | yes | The opaque token returned by esim_create_order. |
No output schema declared.
No examples provided.
esim_create_order ~309
Create a pending order. With `payment_method: "stripe"` (default) you get back a `payment_link_url` — present it to the user to tap and pay on Stripe's hosted page. With `payment_method: "btc"` you get back a `btc` block (on-chain address + amount + QR data URI + expiry) — present the address and amount to the user to pay from any Bitcoin wallet; no redirect. If the user hasn't said how they want to pay, ask: card or Bitcoin. The eSIM QR code arrives at `email` within ~30 seconds of payment clearing. Use `esim_check_order` to poll status.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_source | string | – | Optional: identifier for the calling agent (e.g. 'claude-code', 'cursor'). Used for our analytics; not seen by the buyer. |
| string | yes | Buyer's email address. The eSIM QR code will be delivered here. | |
| payment_method | string | – | How the buyer pays. 'stripe' (default) → hosted card checkout, returns a payment_link_url. 'btc' → on-chain Bitcoin, returns a btc block (address + sats + QR) to show the user directly. BTC may be de… |
| variation_id | number | yes | The specific variation ID to buy (from esim_search_plans or esim_get_plan). |
No output schema declared.
No examples provided.
esim_get_plan ~53
Fetch the full detail of one plan by slug, including all variations (every days × GB permutation with its price).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Plan slug, e.g. 'spain' or 'europe'. |
No output schema declared.
No examples provided.
esim_search_plans ~240
Search the Worldcitisim eSIM catalog. Returns plans matching the given filters (country ISO code, region, desired days, desired GB). Plans have variations — each variation is one specific (days × GB × price) combo. The user picks one variation_id to buy.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Two-letter ISO 3166-1 alpha-2 country code (e.g. 'JP', 'ES', 'US') OR a plan slug ('spain', 'japan', 'europe', 'global'). Matched case-insensitively against plan slugs and display names. |
| limit | number | – | Max plans to return (default 5, max 20). |
| max_days | number | – | Maximum plan duration in days. |
| min_days | number | – | Minimum plan duration in days. |
| min_gb | number | – | Minimum data allowance in GB. Use -1 for 'unlimited'. |
| region | string | – | Region slug: 'europe' | 'mena' | 'caribbean' | 'balkans' | 'latam' | 'asia' | 'global'. |
No output schema declared.
No examples provided.
How do I install the Worldcitisim eSIM MCP server?
Worldcitisim eSIM runs locally as an npm package, launched with npx -y @worldcitisim/mcp-esim. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @worldcitisim/mcp-esim
claude mcp add com-worldcitisim-mcp-esim -- npx -y @worldcitisim/mcp-esim
What is the Worldcitisim eSIM MCP server?
Worldcitisim eSIM is an MCP server listed in the public MCP registry as com.worldcitisim/mcp-esim. Travel eSIMs for 193 countries. Stripe + Bitcoin checkout. QR by email in 30s. No API key. This page covers its npm package (@worldcitisim/mcp-esim).
Is the Worldcitisim eSIM MCP server safe to use?
Worldcitisim eSIM scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Worldcitisim eSIM MCP server expose?
Worldcitisim eSIM exposes 4 tools: esim_search_plans, esim_get_plan, esim_create_order, esim_check_order. Their descriptions and schemas cost roughly 679 tokens of context every time the server is loaded.
Is the Worldcitisim eSIM MCP server still maintained?
Worldcitisim eSIM is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Worldcitisim eSIM MCP server under?
Worldcitisim eSIM declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.