eSIM Eagle Plan Finder
REMOTE · ESIMEAGLE.COM
Find public eSIM plans by destination, trip length, data needs, currency, and locale.
Available components
Last scanned (23 minutes ago)
Scores higher than 99% of remote servers
Reachable. Last reached 6 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 Security100
- 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, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 181 tokens (~181/item across 1 items; 1 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 6 Nov 26 +6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Oct 26 0
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Sept 26 0
- DNSSEC: fail → pass ▲ security
- 13 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
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 6 Nov 2026 · Probed https://esimeagle.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=esimeagle.com | CN=WE1,O=Google Trust Services,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 894c28a1963f2b6213b3e030028363c3 |
| SANs: esimeagle.com, *.esimeagle.com | ||||||
| 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 secure
Validation of esimeagle.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| esimeagle.com. | DS published | 2371 | 13 | Verified |
| esimeagle.com. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://esimeagle.com/mcp | Verified | 200 | |
| http (plaintext) | http://esimeagle.com/mcp | HTTPS enforced | 301 | https://esimeagle.com/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 →
find_esim_plans Find Esim Plans Tool ~145
Finds up to five live eSIM plans that cover every requested country or region, priced for the trip length, data need, currency, and locale. Use the returned checkout URL to buy.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | ISO 4217 display currency code. |
| data_need | string | – | Expected data usage. Recommended assumes about 500 MB per day. |
| destinations | array | yes | One to ten ISO country codes, destination slugs, or exact English destination names, such as JP, japan, or Europe. |
| locale | string | – | Language for destination names, activation guidance, and checkout URLs. |
| trip_days | integer | yes | Number of travel days. |
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | – |
| data_need | string | yes | – |
| destinations | array | yes | – |
| locale | string | yes | – |
| message | string | yes | – |
| plan_count | integer | yes | – |
| plans | array | yes | – |
| recommended_data_mb | integer | yes | – |
| trip_days | integer | yes | – |
No examples provided.
How do I install the eSIM Eagle Plan Finder MCP server?
eSIM Eagle Plan Finder is a hosted endpoint at https://esimeagle.com/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 · esimeagle.com
claude mcp add --transport http com-esimeagle-plans 'https://esimeagle.com/mcp'
What is the eSIM Eagle Plan Finder MCP server?
eSIM Eagle Plan Finder is an MCP server listed in the public MCP registry as com.esimeagle/plans. Find public eSIM plans by destination, trip length, data needs, currency, and locale. This page covers its hosted endpoint (https://esimeagle.com/mcp).
Is the eSIM Eagle Plan Finder MCP server safe to use?
eSIM Eagle Plan Finder scores 96 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 eSIM Eagle Plan Finder MCP server expose?
eSIM Eagle Plan Finder exposes 1 tool: find_esim_plans. Their descriptions and schemas cost roughly 145 tokens of context every time the server is loaded.
Does the eSIM Eagle Plan Finder MCP server require authentication?
No. We connected to eSIM Eagle Plan Finder without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the eSIM Eagle Plan Finder MCP server still maintained?
eSIM Eagle Plan Finder is still listed as active in the MCP registry. We last reached this channel on 6 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 eSIM Eagle Plan Finder MCP server?
VerifyMCP ran 13 checks on eSIM Eagle Plan Finder, 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.