io.github.kakha13/esim-mcp
NPM · ESIM-MCP · SCANNED AUG 14
Compare travel eSIM plans by country, and regional vs local pricing for multi-country trips.
Available components
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 →
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 95 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 9 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 Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · esim-mcp
claude mcp add kakha13-esim-mcp -- npx -y esim-mcp
codex mcp add kakha13-esim-mcp -- npx -y esim-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kakha13-esim-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"esim-mcp"
],
"enabled": true
}
}
} openclaw mcp add kakha13-esim-mcp --command npx --arg -y --arg esim-mcp
mcp_servers:
kakha13-esim-mcp:
command: "npx"
args: ["-y", "esim-mcp"] {
"mcpServers": {
"kakha13-esim-mcp": {
"command": "npx",
"args": [
"-y",
"esim-mcp"
]
}
}
} 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.
- 13 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 11 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 +4
- Known CVEs: partial → pass ▲ security
- Dependency health: partial → 0.85 functional
- 6 Aug 26 +30
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: pass functional
- 5 Aug 26 35
First indexed and scored.
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 14 Aug 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 |
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
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.
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.