Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AeroCell: eSIM Travel Data

REMOTE · AEROCELL.APP

Search live AeroCell travel eSIM plans, prices and coverage for countries and multi-country trips.

Available components

+3 this week 74 Trust /100

Last scanned (3 hours ago)

Scores higher than 66% of remote servers

Reachable. Last reached 23 Oct 2026.

Category E-commerce

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 535 tokens (~178/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 Management33
  • Stability observed for 10 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
  • 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 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Oct 26 0
    • Tool “find_regional_esim_plans” rewrote its description, which is the text the model reads security
    • Tool “get_esim_plan” rewrote its description, which is the text the model reads security
  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 13 Oct 26 70

    First indexed and scored.

Diagnostics

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 23 Oct 2026 · Probed https://aerocell.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aerocell.app CN=YE1,O=Let's Encrypt,C=US 12 Sept 2026 11 Dec 2026 ECDSA 256 ECDSA-SHA384 532b9b6a1e19a66f742209f426174e5bc49
SANs: *.aerocell.app, aerocell.app
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of aerocell.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
aerocell.app. absent 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://aerocell.app/mcp Verified 200
http (plaintext) http://aerocell.app/mcp HTTPS enforced 301 https://aerocell.app/mcp
MCP tools · 3 exposed · ~472 tokens

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 →

Tool Tokens
find_esim_plans ~190

Find current AeroCell travel eSIM plans for one country. Use a two-letter ISO country code. Provide both travel dates if known; plans covering the whole trip are returned by default. Optional data and USD price filters narrow results.

NameTypeReqDescription
country_codestringyesTwo-letter ISO country code, such as JP; XK is also supported by the catalog.
end_datestring–Trip end, YYYY-MM-DD inclusive. Provide with start_date.
limitinteger–Maximum results, 1–20; default 8.
max_price_usdnumber–Maximum price in USD.
min_data_gbnumber–Minimum data allowance in GB.
require_trip_coverageboolean–Defaults to true when dates are supplied; false includes shorter plans.
start_datestring–Trip start, YYYY-MM-DD. Provide with end_date.
NameTypeReqDescription
browse_urlstringyes–
countryobjectyes–
currencystringyes–
notestringyes–
plansarrayyes–
total_matchingnumberyes–
trip_daysnumber|nullyes–
updated_atstringyes–

No examples provided.

find_regional_esim_plans ~202

Find live multi-country AeroCell bundles. Supply every itinerary country as a two-letter ISO code; only bundles listing all those countries are returned. Optionally select a named region. A region-only search returns bundles with their exact country coverage.

NameTypeReqDescription
country_codesarray–Every itinerary country, up to 30 distinct codes.
end_datestring–Trip end, YYYY-MM-DD inclusive. Provide with start_date.
limitinteger–Maximum results, 1–20; default 8.
max_price_usdnumber–Maximum price in USD.
min_data_gbnumber–Minimum data allowance in GB.
regionstring–Optional named catalog region; check returned country_codes.
require_trip_coverageboolean–Defaults to true when dates are supplied; false includes shorter plans.
start_datestring–Trip start, YYYY-MM-DD. Provide with end_date.
NameTypeReqDescription
browse_urlstringyes–
currencystringyes–
notestringyes–
plansarrayyes–
regionstring|nullyes–
requested_country_codesarrayyes–
total_matchingnumberyes–
trip_daysnumber|nullyes–
updated_atstringyes–

No examples provided.

get_esim_plan ~80

Get current details and an AeroCell checkout link for a plan ID from a single-country search. Requires the same country code.

NameTypeReqDescription
country_codestringyesTwo-letter ISO country code, such as JP; XK is also supported by the catalog.
plan_idstringyesPlan ID from a country search; requires the same country_code.
NameTypeReqDescription
countryobjectyes–
currencystringyes–
notestringyes–
planobjectyes–
updated_atstringyes–

No examples provided.

Install

How do I install the AeroCell: eSIM Travel Data MCP server?

AeroCell: eSIM Travel Data is a hosted endpoint at https://aerocell.app/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 · aerocell.app

# add to Claude Code
claude mcp add --transport http mezsondra-aerocell 'https://aerocell.app/mcp'
Common questions

What is the AeroCell: eSIM Travel Data MCP server?

AeroCell: eSIM Travel Data is an MCP server listed in the public MCP registry as io.github.Mezsondra/aerocell. Search live AeroCell travel eSIM plans, prices and coverage for countries and multi-country trips. This page covers its hosted endpoint (https://aerocell.app/mcp).

Is the AeroCell: eSIM Travel Data MCP server safe to use?

AeroCell: eSIM Travel Data scores 74 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 AeroCell: eSIM Travel Data MCP server expose?

AeroCell: eSIM Travel Data exposes 3 tools: find_esim_plans, get_esim_plan, find_regional_esim_plans. Their descriptions and schemas cost roughly 472 tokens of context every time the server is loaded.

Does the AeroCell: eSIM Travel Data MCP server require authentication?

No. We connected to AeroCell: eSIM Travel Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AeroCell: eSIM Travel Data MCP server still maintained?

AeroCell: eSIM Travel Data is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.