Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
esimgomobile — Travel eSIM Tools is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
36
tools declared
remote
at its publisher
—
calls last 7d
What it does
Travel eSIM plan catalog, coverage and trip-planning tools for agents and developers.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http esimgomobile-travel-esim-tools-mcp https://mcp.esimgomobile.com/mcp
# 2 — ask your agent for something these tools do
# run_speed_test, get_public_ip, check_roaming_status and 33 more
esimgomobile — Travel eSIM Tools costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ESAll 1 server
esimgomobile1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http esimgomobile-travel-esim-tools-mcp https://mcp.esimgomobile.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
36 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Use when the user wants to measure their current internet speed. Runs a real download/ping measurement in the interactive widget and reports Mbps, ping, and a quality grade.
No parameter schema on file.
Use when the user asks for their public IP address. Returns the IP address the request arrives from, as seen by the server edge.
No parameter schema on file.
Use when the user wants to know whether they are currently roaming. Compares their home country against the country they are in now.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| home_country | string | yes | User's home country, e.g. United States |
| current_country | string | yes | Country the user is currently in |
Use when the user wants the network latency to a host. Performs a real HTTPS HEAD request from the deployment edge and reports round-trip time to first byte in milliseconds.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| destination | string | yes | Hostname or public IP to probe, e.g. example.com or 8.8.8.8 |
Use when the user gives you download/upload speed and ping numbers and wants a verdict. Grades the connection Excellent/Good/Fair/Poor with practical advice.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| download_mbps | number | yes | Download speed in Mbps |
| upload_mbps | number | yes | Upload speed in Mbps |
| ping_ms | number | yes | Ping in milliseconds |
Use when the user is on hotel/airport/cafe Wi-Fi and suspects a login page is blocking them. Gives a step-by-step guided check — no automatic probing.
No parameter schema on file.
Use when the user wants to check whether their DNS queries leak outside their VPN. Gives a guided manual check — browsers cannot run automatic DNS probes.
No parameter schema on file.
Use when the user is about to use public, hotel, or airport Wi-Fi. Returns a practical safety checklist.
No parameter schema on file.
Use when the user asks how much bandwidth an activity needs (video calls, 4K streaming, gaming). Looks up reference requirements from a built-in table.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| activity | string | yes | Activity, e.g. '4K streaming', 'video calls', 'gaming' |
Use when the user asks whether a country is covered by esimgomobile plans. Answers from esimgomobile's own published plan catalog (live-checked) plus the built-in country network reference.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | Country to check, e.g. Japan |
Use when the user is planning a trip and asks how much mobile data they need. Estimates from trip days, daily hours online, and a light/moderate/heavy usage profile, then suggests a plan size.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | number | yes | Trip length in days |
| hours_per_day | number | yes | Hours online per day |
| usage_profile | string | yes | Usage profile |
Use when the user wants to compare their home carrier's roaming fees against a travel eSIM. Compares a user-supplied carrier day-pass rate with an illustrative travel-eSIM daily rate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | number | yes | Trip length in days |
| home_carrier_daily_rate_usd | number | yes | Home carrier roaming day-pass price in USD |
Use when the user has a multi-country itinerary and asks which eSIM plan type fits. Recommends single-country vs regional vs global plans from the country list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| countries | array | yes | Countries on the itinerary |
Use when the user asks whether their phone supports eSIM. Checks the model against a built-in device table, with a manual fallback check.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| device_model | string | yes | Device model, e.g. 'iPhone 13', 'Galaxy S23' |
Use when the user needs to check whether their phone is carrier-unlocked (required for travel eSIMs). Walks through the check on iPhone and Android.
No parameter schema on file.
Use when the user asks which mobile network is best in a specific city. Ranks operators by observed cell-tower density from the OpenCelliD open dataset — a coverage proxy, not a speed measurement.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| city | string | yes | City, e.g. Tokyo |
| country | string | yes | Country, e.g. Japan |
Use when the user asks about connectivity at an airport (Wi-Fi, SIM vendors, eSIM tips). Answers from a researched dataset of major international airports: free Wi-Fi details, where to buy a SIM, and eSIM options on arrival.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| airport_code | string | yes | IATA airport code, e.g. NRT |
Use when the user asks where to find free Wi-Fi in a city. Queries the live OpenStreetMap directory (Nominatim geocoding + Overpass) for community-mapped free Wi-Fi hotspots near the city.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| city | string | yes | City to search in |
Use when the user asks about mobile networks, eSIM support, or Wi-Fi in a country. Returns a fact sheet from a built-in table, with general guidance where a country isn't listed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | Country, e.g. Japan |
Use when the user asks about internet restrictions in a country (VoIP blocks, firewalls). Returns a high-level snapshot from a built-in table — not legal advice.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | Country, e.g. UAE |
Use when the user needs step-by-step eSIM installation instructions. Covers iPhone and Android, via QR code or manual entry.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| os | string | yes | Phone OS |
| method | string | yes | Install method |
Use when the user's eSIM isn't working. Diagnoses common problems: no service, no data, slow data, QR issues, activation failures, calls not working.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symptom | string | yes | What is going wrong |
Use when the user needs APN settings for a carrier after installing an eSIM. Looks up a built-in APN table; most travel eSIMs configure automatically.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| carrier | string | yes | Carrier or region, e.g. T-Mobile, UK, EU roaming |
Use when the user runs a home line plus a travel eSIM and needs the right configuration. Explains which line handles data, calls, and iMessage, and how to avoid roaming charges.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| primary_use | string | no | Main goal, e.g. 'keep my number reachable', 'cheapest data' |
Use when the user wants to stretch a travel data plan. Gives OS-specific steps: low-data mode, background limits, offline maps and downloads.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| os | string | yes | Phone OS |
Use when the user needs to dial a local number internationally. Formats a local phone number for calling between two countries, using a built-in dialing-code table.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from_country | string | yes | Country you're calling from |
| to_country | string | yes | Country you're calling to |
| phone_number | string | yes | Local number as written locally, e.g. 06 12 34 56 78 |
Use when the user asks how much of their plan data is left or how to ration it over a trip. Computes remaining data, daily budget and end-of-trip projection from the plan size and usage so far (which the user's phone reports exactly).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_gb | number | yes | Plan size in GB, e.g. 5 |
| used_gb | number | yes | Data already used in GB — the phone shows this in Settings > Cellular / Network & Internet |
| days_total | number | no | Trip or validity length in days |
| days_elapsed | number | no | Days already gone |
Use when the user asks what esimgomobile plans exist or what an eSIM costs. Lists the real, currently published plan catalog with USD prices (live-checked against esimgomobile.com).
No parameter schema on file.
Use when the user says where they're going, for how long, and roughly how much they'll use data, and wants a concrete plan pick. Estimates the GB need, then picks the cheapest matching plan from the real published catalog with prices.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| countries | array | yes | Countries on the itinerary |
| days | number | yes | Trip length in days |
| usage_profile | string | yes | Usage profile |
Use when the user is preparing a trip and wants one pass over everything data-related for a country: networks, eSIM support, internet freedom, device check and install steps. Composes the built-in country, freedom, device and install references.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | Destination country |
| os | string | no | Phone OS for install steps (default ios) |
| device_model | string | no | Phone model for a compatibility check |
Use when the user wants to browse or filter esimgomobile plans - by type (data packs, monthly, day passes), max price, minimum GB, coverage scope, or cheapest per-GB. Reads the live published catalog (snapshot fallback, labeled).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | Plan type filter (default all) |
| max_price_usd | number | no | Only plans at or under this USD price |
| min_gb | number | no | Only plans with at least this many GB (fair-use plans always match) |
| scope | string | no | Coverage scope filter (default any) |
| sort | string | no | Sort order (default price) |
Use when the user asks about one specific esimgomobile plan by id - price, data allowance, validity, coverage scope, per-GB unit price, and where to buy.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | Plan id, e.g. data-pack-20gb (see search_plans for ids) |
Use when the user is choosing between 2-4 esimgomobile plans. Side-by-side price, data, validity, scope and per-GB unit price, with a best-value pick. No competitor API offers this.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_ids | array | yes | 2-4 plan ids to compare (see search_plans) |
Use when the user is about to buy and wants everything checked first - the eSIM Go validate-style dry run. Verifies the plan id exists, quantity (1-50), device eSIM compatibility, and single-country scope against the itinerary, then gives a published-price estimate. Places no order and charges nothing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | Plan id (see search_plans) |
| quantity | integer | no | Quantity 1-50 (default 1) |
| device_model | string | no | Phone model for an eSIM compatibility check |
| countries | array | no | Destination countries, for scope validation |
Use when the user gives an itinerary (countries + days + usage) and wants the full answer in one call: estimated data need, best published plan pick with an alternative, and a per-country networks/eSIM/freedom brief. Composite over the live catalog and built-in country references.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| countries | array | yes | Countries on the itinerary, in order |
| days | number | yes | Trip length in days |
| usage_profile | string | yes | Usage profile |
Use when the user asks which mobile networks operate in a country, or for eSIM support / Wi-Fi / internet-freedom facts for one country - the eSIM Go /networks parity endpoint, from esimgomobile's built-in reference.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | Country name, e.g. Japan |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install esimgomobile — Travel eSIM Tools or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 0.1.0 · scanned 22 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest0ed1bff7142bde3516799d069a5314cb39c98cb3ab2e34b81752211cfe74d0b5
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| run_speed_test | untrusted-input | untrusted-input: keyword "download", declares openWorldHint: true (interacts with entities outside the server) |
| get_public_ip | no tags | |
| check_roaming_status | no tags | |
| measure_latency | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| grade_connection_quality | untrusted-input | untrusted-input: keyword "download" |
| detect_captive_portal | no tags | |
| check_dns_leaks | no tags | |
| get_wifi_security_checklist | no tags | |
| lookup_speed_requirements | no tags | |
| check_coverage | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| estimate_data_usage | no tags | |
| calculate_roaming_cost | no tags | |
| plan_multi_country_esim | no tags | |
| check_device_compatibility | no tags | |
| check_carrier_lock | no tags | |
| find_best_network | no tags | |
| get_airport_connectivity | no tags | |
| find_free_wifi | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_country_fact_sheet | no tags | |
| check_internet_freedom | no tags | |
| get_installation_guide | no tags | |
| troubleshoot_esim | no tags | |
| lookup_apn_settings | no tags | |
| setup_dual_sim | no tags | |
| setup_data_saver | no tags | |
| format_international_number | no tags | |
| calculate_data_budget | no tags | |
| list_available_plans | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| recommend_plan | no tags | |
| get_travel_data_checklist | no tags | |
| search_plans | untrusted-input | untrusted-input: keyword "browse", declares openWorldHint: true (interacts with entities outside the server) |
| get_plan_details | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| compare_plans | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| validate_order_draft | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| plan_trip | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_country_networks | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest0ed1bff7142bde35
Scanned2026-10-22
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish esimgomobile — Travel eSIM Tools can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.