io.github.kakha13/esim-mcp
NPM · ESIM-MCP
Compare travel eSIM plans by country, and regional vs local pricing for multi-country trips.
Available components
Last scanned (13 hours ago)
Scores higher than 87% 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
- 31 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 78 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 470 tokens (~94/item across 5 items; 5 tools + 0 resources), lean.Pass
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- 21 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.80 functional
- 15 Oct 26 +1
- Stability: 0.97 → pass security
- 13 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 12 Oct 26 −2
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.90 functional
- 8 Oct 26 +2
- Stability: 0.87 → 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 22 Oct 2026 · Analysed npm/esim-mcp@0.1.1
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 | 31 |
| 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 →
get_plan_coverage ~70
List every country a regional or global plan covers. Takes the group_id from a plan returned by plan_trip or list_plans. Local plans have a null group_id and cover only their own country.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | integer | yes | The plan group id, from a plan's group_id field |
No output schema declared.
No examples provided.
list_plans ~110
List eSIM plans for one country, cheapest first. Use plan_trip instead when the user is visiting more than one country.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO country code such as JP, or a slug such as south-korea |
| days | integer | – | Only plans lasting at least this many days |
| limit | integer | – | How many plans to return, default 20 |
| min_data_gb | number | – | Only plans with at least this much data. Unlimited plans always qualify |
No output schema declared.
No examples provided.
list_popular_destinations ~65
List the destinations travellers buy eSIMs for most often, with a starting price for each. Use this only when the user has not named a destination and wants ideas. If they already named one country use list_plans, and if they named several use plan_trip.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plan_trip ~131
Work out the cheapest way to stay connected across several countries. Compares one regional plan covering the whole trip against buying a local plan per country, and says which is cheaper. Use this whenever the user names more than one destination.
| Name | Type | Req | Description |
|---|---|---|---|
| countries | array | yes | Two-letter ISO country codes, for example ["JP", "KR", "TW"]. This tool does not accept country names or slugs: call search_destinations first to get the code. |
| days | integer | – | Trip length in days |
| min_data_gb | number | – | Minimum data per plan, in GB. Unlimited plans always qualify |
No output schema declared.
No examples provided.
search_destinations ~94
Find countries CheapereSIM sells eSIM plans for, by full or partial name. Use this when the user names a place and you need its country code before looking up plans. Do not use it to compare prices or list plans: use list_plans for a single country, or plan_trip for several.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Country name or partial name, for example "jap" or "south kor" |
No output schema declared.
No examples provided.
How do I install the io.github.kakha13/esim-mcp server?
io.github.kakha13/esim-mcp runs locally as an npm package, launched with npx -y esim-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · esim-mcp
claude mcp add kakha13-esim-mcp -- npx -y esim-mcp
What is the io.github.kakha13/esim-mcp server?
io.github.kakha13/esim-mcp is listed in the public MCP registry as io.github.kakha13/esim-mcp. Compare travel eSIM plans by country, and regional vs local pricing for multi-country trips. This page covers its npm package (esim-mcp).
Is the io.github.kakha13/esim-mcp server safe to use?
io.github.kakha13/esim-mcp scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 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 io.github.kakha13/esim-mcp server expose?
io.github.kakha13/esim-mcp exposes 5 tools: search_destinations, list_plans, list_popular_destinations, plan_trip, get_plan_coverage. Their descriptions and schemas cost roughly 470 tokens of context every time the server is loaded.
Is the io.github.kakha13/esim-mcp server still maintained?
io.github.kakha13/esim-mcp is still listed as active in the MCP registry. We last reached this channel on 22 October 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 io.github.kakha13/esim-mcp server under?
io.github.kakha13/esim-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.