shibaSIM eSIM Plans
REMOTE · SHIBASIM.NET
Read-only travel eSIM plan lookup (USD prices) that links buyers to shibaSIM checkout.
Available components
Last scanned (6 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 406 tokens (~135/item across 3 items; 3 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 Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% 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 3 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 4 Nov 26 68
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 5 Nov 2026 · Probed https://shibasim.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=shibasim.net | CN=WE1,O=Google Trust Services,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 8a91bd139197f9830e57aaea10a330d9 |
| SANs: shibasim.net, *.shibasim.net | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of shibasim.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| net. | DS published | 37331 | 13 | Verified |
| shibasim.net. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://shibasim.net/mcp | Verified | 200 | |
| http (plaintext) | http://shibasim.net/mcp | HTTPS enforced | 301 | https://shibasim.net/mcp |
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 Get plan details ~64
Full details of one plan by id (from search_plans): data, validity, daily cap and reduced speed, covered countries, hotspot, top-up availability, verified network facts, USD price and checkout_url.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Plan id returned by search_plans. |
No output schema declared.
No examples provided.
list_destinations List destinations ~66
List destinations (countries and multi-country regions) with eSIM plans on shibaSIM: code, name, ISO country codes covered, plan count and cheapest USD price.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional name/ISO filter, e.g. 'japan' or 'JP'. |
No output schema declared.
No examples provided.
search_plans Search eSIM plans ~221
Search shibaSIM travel eSIM plans for one destination with factual filters. Prices are USD. Each result has a checkout_url that sends the buyer to shibaSIM. Per-day plans are filtered on GB/day, fixed plans on total GB.
| Name | Type | Req | Description |
|---|---|---|---|
| data_type | string | – | Only daily-allowance plans or only fixed total-data plans. |
| destination | string | yes | Destination name, ISO country code or destination code from list_destinations, e.g. 'Japan' or 'JP'. |
| five_g | boolean | – | true = only plans where 5G is verified on shibaSIM. |
| hotspot | boolean | – | true = only plans that allow hotspot/tethering. |
| limit | integer | – | Default 10. |
| max_price_usd | number | – | – |
| min_data_gb | number | – | Minimum GB (GB per day for per-day plans, total GB for fixed plans). |
| min_validity_days | integer | – | – |
| sort | string | – | cheapest = lowest price; value = lowest USD per GB. |
No output schema declared.
No examples provided.
How do I install the shibaSIM eSIM Plans MCP server?
shibaSIM eSIM Plans is a hosted endpoint at https://shibasim.net/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · shibasim.net
claude mcp add --transport http net-shibasim-esim 'https://shibasim.net/mcp'
What is the shibaSIM eSIM Plans MCP server?
shibaSIM eSIM Plans is an MCP server listed in the public MCP registry as net.shibasim/esim. Read-only travel eSIM plan lookup (USD prices) that links buyers to shibaSIM checkout. This page covers its hosted endpoint (https://shibasim.net/mcp).
Is the shibaSIM eSIM Plans MCP server safe to use?
shibaSIM eSIM Plans scores 69 out of 100 on VerifyMCP. 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 shibaSIM eSIM Plans MCP server expose?
shibaSIM eSIM Plans exposes 3 tools: list_destinations, search_plans, get_plan. Their descriptions and schemas cost roughly 351 tokens of context every time the server is loaded.
Does the shibaSIM eSIM Plans MCP server require authentication?
No. We connected to shibaSIM eSIM Plans without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the shibaSIM eSIM Plans MCP server still maintained?
shibaSIM eSIM Plans 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 did VerifyMCP test on the shibaSIM eSIM Plans MCP server?
VerifyMCP ran 13 checks on shibaSIM eSIM Plans, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.