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.

Simcardo Travel eSIM

REMOTE · SIMCARDO.COM

Browse Simcardo's live eSIM catalogue and quote dated trips. No account, 51 storefront languages.

Available components

+3 this week 73 Trust /100

Last scanned (7 minutes ago)

Scores higher than 59% of remote servers

Reachable. Last reached 22 Nov 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
  • 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
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 831 tokens (~277/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 Management37
  • Stability observed for 11 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
  • 80% of tool parameters carry a description.Partial
  • Structured output schemas are declared (33% 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
What we tested

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 →

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.

  • 21 Nov 26 +1

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

  • 19 Nov 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.

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 13 Nov 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.

  • 12 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 11 Nov 26 68

    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 22 Nov 2026 · Probed https://simcardo.com/mcp-travel-esim

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=simcardo.com CN=WE1,O=Google Trust Services,C=US 4 Nov 2026 2 Feb 2027 ECDSA 256 ECDSA-SHA256 42224bb6c65180f00e5ac2a231ef9cd6
SANs: simcardo.com, *.simcardo.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 insecure

Validation of simcardo.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
simcardo.com. 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
Header Value
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://simcardo.com/mcp-travel-esim Verified 200
http (plaintext) http://simcardo.com/mcp-travel-esim HTTPS enforced 301 https://simcardo.com/mcp-travel-esim
MCP tools · 3 exposed · ~653 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
list_esim_destinations ~123

Discover countries, territories and regional/global packages. Coverage-only territories have no dedicated storefront. Returns active languages, counts, localized names and canonical links where available. Paginate with next_after_market. Use quote_travel_esim for dates and hotspot.

NameTypeReqDescription
after_marketstring–Copy next_after_market from the previous page, with the same scope.
languagestring–Storefront language for localized destination names, price display and links. Reply to the traveler in their language.
page_sizeinteger––
scopestring––

No output schema declared.

No examples provided.

list_esim_plans ~197

Browse every current public plan, optionally by country/territory market (e.g. JP), package slug (e.g. europe-extra), or exact SKU. Returns localized links, retail total, coverage codes, validity and supplier facts, including explicit unknowns. Browse results are not travel recommendations; use quote_travel_esim to verify trip requirements. Paginate with next_after_sku.

NameTypeReqDescription
after_skustring–Copy next_after_sku from the previous page, with the same filters.
currencystring––
languagestring–Storefront language for localized destination names, price display and links. Reply to the traveler in their language.
marketstring–Market returned by list_esim_destinations. Omit to browse all markets.
page_sizeinteger––
skustring–Exact SKU to retrieve; do not use with market or after_sku.

No output schema declared.

No examples provided.

quote_travel_esim ~333

Find current Simcardo eSIM plans for a dated trip. Use when the traveler needs a plan that covers a destination, trip duration, data allowance or tethering requirement. Return verified matches with total price, activation terms and a direct product link, or explain why no plan can be confirmed.

NameTypeReqDescription
additional_destinationsarray–Add other country codes to find one eSIM with verified coverage in every listed country for the full date range.
currencystringyesStorefront currency code, e.g. EUR, USD, JPY, THB or CZK.
data_gbnumber–Total requested GB for the entire trip; 1 GB = 1000 MB. Provide this OR usage_profile.
destinationstringyesUppercase country or territory code, e.g. TH, JP, US, BR. Ask for clarification rather than guessing.
end_datestringyesLast local calendar day, included (YYYY-MM-DD).
hotspot_requiredboolean–True requires explicit supplier confirmation that tethering is allowed for the exact plan.
include_regionalboolean–For a single destination, also consider packages with verified coverage there. Defaults to dedicated country plans only.
languagestring–Storefront language for localized destination names, price display and links. Reply to the traveler in their language.
start_datestringyesFirst local calendar day of coverage (YYYY-MM-DD).
usage_profilestring–Choose this when the traveler described usage rather than specifying GB. The catalogue estimates the required GB. Do not send both.
NameTypeReqDescription
catalogue_checked_atstringyes–
destination_urlstring|nullyes–
notestringyes–
plansarrayyes–
reason_codesarrayyes–
requestobjectyes–
statusstringyes–

No examples provided.

Install

How do I install the Simcardo Travel eSIM MCP server?

Simcardo Travel eSIM is a hosted endpoint at https://simcardo.com/mcp-travel-esim, 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 · simcardo.com

# add to Claude Code
claude mcp add --transport http com-simcardo-travel-esim 'https://simcardo.com/mcp-travel-esim'
Common questions

What is the Simcardo Travel eSIM MCP server?

Simcardo Travel eSIM is an MCP server listed in the public MCP registry as com.simcardo/travel-esim. Browse Simcardo's live eSIM catalogue and quote dated trips. No account, 51 storefront languages. This page covers its hosted endpoint (https://simcardo.com/mcp-travel-esim).

Is the Simcardo Travel eSIM MCP server safe to use?

Simcardo Travel eSIM scores 73 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 Simcardo Travel eSIM MCP server expose?

Simcardo Travel eSIM exposes 3 tools: quote_travel_esim, list_esim_destinations, list_esim_plans. Their descriptions and schemas cost roughly 653 tokens of context every time the server is loaded.

Does the Simcardo Travel eSIM MCP server require authentication?

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

Is the Simcardo Travel eSIM MCP server still maintained?

Simcardo Travel eSIM is still listed as active in the MCP registry. We last reached this channel on 22 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 Simcardo Travel eSIM MCP server?

VerifyMCP ran 13 checks on Simcardo Travel eSIM, 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.