GLOBALCELL eSIM
REMOTE · MCP.GLOBALCELL.DEV · 2 COMPONENTS
Travel eSIMs for 130+ countries: plan a trip, compare plans, buy, install and diagnose.
Available components
Last scanned (4 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
Recent critical change
Authorization (5 Nov 2026). See the changelog before you install this server.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (create_order). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1386 tokens (~86/item across 16 items; 12 tools + 4 resources), lean.Pass
- 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 Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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
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 −6
- Authorization: partial → fail ▼ critical
- Tool “create_order” rewrote its description, which is the text the model reads security
- Tool “create_order” is now declared destructive security
- Prompt “top_up_data” was removed ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New prompt “add_data_package” functional
- 4 Nov 26 73
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://mcp.globalcell.dev
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.globalcell.dev | CN=YE2,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6001c2e870bba7e2c469098fc82cf9709e8 |
| SANs: mcp.globalcell.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 mcp.globalcell.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| globalcell.dev. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.globalcell.dev | Verified | 200 | |
| http (plaintext) | http://mcp.globalcell.dev | HTTPS enforced | 308 | https://mcp.globalcell.dev/ |
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 →
check_device Check a phone for eSIM ~61
Whether a phone, tablet or watch model supports eSIM, from a list of known models, with how to check on the device itself.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | e.g. "iPhone 13", "Galaxy S23", "Pixel 8" |
No output schema declared.
No examples provided.
check_order Check order ~47
Order status. Once "fulfilled", a new eSIM includes its install links, QR code link and manual codes.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | string | yes | – |
| orderToken | string | yes | – |
No output schema declared.
No examples provided.
check_usage Check data left ~46
Data used and left on the eSIM of a fulfilled order, per package, with start and expiry dates.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | string | yes | – |
| orderToken | string | yes | – |
No output schema declared.
No examples provided.
compare_plans Compare plans ~51
Side-by-side comparison of 2 to 5 plans: data, days, price per GB and per day, countries and hotspot.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | – |
| skus | array | yes | – |
No output schema declared.
No examples provided.
country_networks Networks in a country ~54
The mobile networks GLOBALCELL eSIMs use in a country, how many plans work there and the lowest price.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO code like "SK" or a country name like "Slovakia" |
No output schema declared.
No examples provided.
create_order Create order ~155
Creates an order and returns checkoutUrl, the page where the user pays; nothing is charged by this call. Without confirm: true it only returns a preview with the price and creates nothing. Returns orderId and orderToken for check_order.
| Name | Type | Req | Description |
|---|---|---|---|
| activation | – | – | Default { "mode": "now" } |
| confirm | boolean | – | Leave out first to get a preview; call again with true once the user agreed |
| currency | string | yes | EUR or USDT |
| customerEmail | string | – | Optional; for the receipt |
| iccid | string | – | Required for type "package": the ICCID of the eSIM to add data to |
| sku | string | yes | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
diagnose_esim Diagnose an eSIM ~73
Why an eSIM may not work: line state, every package (started, data left, expired) and the last mobile network the phone registered on, with the likely cause and the fix. For the eSIM of a fulfilled order.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | string | yes | – |
| orderToken | string | yes | – |
No output schema declared.
No examples provided.
get_plan Get plan ~28
One plan with prices and every country and mobile network it covers.
| Name | Type | Req | Description |
|---|---|---|---|
| sku | string | yes | – |
No output schema declared.
No examples provided.
install_help Install help ~50
Step-by-step eSIM installation and first-use help for iPhone or Android, and fixes for common problems.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | yes | – |
| problem | string | – | Leave empty for the install steps |
No output schema declared.
No examples provided.
list_plans List plans ~167
Plans that work in a country or region, cheapest first, with optional filters for data, days and price.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO code like "SK" or a country name like "Slovakia" |
| currency | string | – | Show and sort prices in this currency (EUR or USDT) |
| limit | integer | – | Default 30 |
| maxPriceMinor | integer | – | Upper price limit in minor units (cents) of the chosen currency |
| minDataGB | number | – | – |
| minDays | integer | – | – |
| purpose | string | – | new_esim: a new eSIM. package: add data to an existing eSIM |
| region | string | – | Region name from search_destinations, e.g. "Europe+" |
No output schema declared.
No examples provided.
recommend_plans Recommend plans for a trip ~183
Plans for a trip to one or more countries: estimates the data needed from the days and how the user uses their phone, then suggests the best-value plans that cover every country for the whole trip.
| Name | Type | Req | Description |
|---|---|---|---|
| countries | array | yes | Every country the user will visit |
| currency | string | – | Show and sort prices in this currency (EUR or USDT) |
| dataGB | number | – | Data the user wants, if they know it; overrides usage |
| days | integer | yes | Length of the trip in days |
| newEsim | boolean | – | Default true. false: the user already has a GLOBALCELL eSIM |
| usage | string | – | light: maps, messaging, email, a little browsing; normal: plus social media, photos and some music; heavy: plus video, video calls or sharing data with a laptop. Default normal |
No output schema declared.
No examples provided.
search_destinations Search destinations ~50
Countries and regions with eSIM plans, with the lowest price per currency. Leave query empty to list all.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Part of a country or region name, or an ISO code |
No output schema declared.
No examples provided.
How do I install the GLOBALCELL eSIM MCP server?
GLOBALCELL eSIM is a hosted endpoint at https://mcp.globalcell.dev/, 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 · mcp.globalcell.dev
claude mcp add --transport http dev-globalcell-mcp 'https://mcp.globalcell.dev/'
What is the GLOBALCELL eSIM MCP server?
GLOBALCELL eSIM is an MCP server listed in the public MCP registry as dev.globalcell/mcp. Travel eSIMs for 130+ countries: plan a trip, compare plans, buy, install and diagnose. This page covers its hosted endpoint (https://mcp.globalcell.dev).
Is the GLOBALCELL eSIM MCP server safe to use?
GLOBALCELL eSIM scores 67 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 GLOBALCELL eSIM MCP server expose?
GLOBALCELL eSIM exposes 12 tools: search_destinations, list_plans, get_plan, recommend_plans, compare_plans, and 7 more. Their descriptions and schemas cost roughly 965 tokens of context every time the server is loaded.
Does the GLOBALCELL eSIM MCP server require authentication?
No. We connected to GLOBALCELL eSIM without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GLOBALCELL eSIM MCP server still maintained?
GLOBALCELL eSIM 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.