SimFuse eSIM Storefront MCP server
app.simfuse/esim-storefrontsimfuse.appstreamable-httpv1.2.0Scanned
Travel eSIMs for 200+ countries. Browse plans, price a multi-country trip, and open a checkout.
15 tools: 5 change things and 10 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the SimFuse eSIM Storefront MCP server can do
The SimFuse eSIM Storefront MCP server is published by simfuse.app, a domain the MCP Registry verified. It has 15 tools. It can create or change data (5 tools: plan-trip, build-plan, check-coverage, create-checkout-session and 1 more), but cannot delete data. 10 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 7, 2026, version 1.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
15 tools
Changes things 5Claude Code: ask
build-planBuild an eSIM plan to the traveller's liking for one destination: how much data, for how many days, optionally which network it runs on and whether calls and texts are bundled.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Build an eSIM plan to the traveller's liking for one destination: how much data, for how many days, optionally which network it runs on and whether calls and texts are bundled. Returns the one real plan that matches, with its id and live price, never a made-up combination: a shape nobody sells is snapped to the nearest one that is, one axis at a time, and every change is spelled out in `adjustments` so you can read it back. Use it when the traveller knows what they want ("10 GB on Docomo for two weeks"); use plan-trip when they want a recommendation or the trip has several countries. To buy, pass `plan.id` to get-checkout-link when a person is paying, or to create-checkout-session when you are. Read-only: it reserves nothing and charges nothing.
Annotations the server declares
- title: Build an eSIM plan
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
check-coverageAnswer "does this eSIM plan work in X?" for one destination, as a yes or no rather than a country list.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Answer "does this eSIM plan work in X?" for one destination, as a yes or no rather than a country list. Takes a plan id and a destination (a country name or two-letter code). Reports whether the destination is covered, and separately whether it is explicitly excluded from an otherwise regional plan. Use get-plan-coverage when you need the full list of countries instead.
Annotations the server declares
- title: Check plan coverage for a destination
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
check-esim-usageHow much data an eSIM has used and how much is left, for one eSIM on a paid order.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it How much data an eSIM has used and how much is left, for one eSIM on a paid order. Identified by the order id and the email that bought it, plus the ICCID from get-order-status or get-esim-activation. Allowances are in megabytes. Readings are served from a cache refreshed every couple of minutes: checked_at says when the reading was taken. An unlimited plan reports its full-speed allowance for the current period rather than a total.
Annotations the server declares
- title: Check eSIM data usage
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
create-checkout-sessionOpen a checkout session for one or more eSIM plans at frozen prices, using the plan ids that plan-trip, list-plans or get-plan returned.No findings
Why it is in this group
- The name "create-checkout-session" says "create": a word for a change.
Description, as the server wrote it Open a checkout session for one or more eSIM plans at frozen prices, using the plan ids that plan-trip, list-plans or get-plan returned. Use it once the traveller has chosen what to buy. It CHARGES NOTHING and reserves no stock: it prices the basket, freezes those prices until the session's price_locked_until, and hands back the session plus a bearer agent key. Payment, completion and cancellation happen afterwards over the SimFuse agentic HTTP API with that key, as the session's `note` explains, and the eSIM is delivered by email once payment settles. Each call opens a NEW session and mints a NEW key, so call it once per basket rather than retrying it to re-read one.
Annotations the server declares
- title: Create checkout session
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
plan-tripAnswer "which eSIM should I buy for this trip?".No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Answer "which eSIM should I buy for this trip?". Give it the stops, a country code and the days spent in each, and it compares one plan covering the whole route against one plan per country against a mix of the two, on live prices, then flags the cheapest option that covers everything and explains the choice in a sentence you can quote. It also estimates the data each stop needs, names any country SimFuse cannot cover, and returns package ids that go straight into create-checkout-session. Use it whenever a trip has two or more countries, and for a single country when the traveller wants a recommendation rather than a list. Read-only: nothing is reserved and nothing is charged, and the totals are today's catalog prices, not a quote held for later.
Annotations the server declares
- title: Plan eSIMs for a trip
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 10Show 10 read-only tools
get-checkout-linkGet the page where a person buys one specific eSIM plan, for an assistant to hand them a link.No findings
Why it is in this group
- The name "get-checkout-link" says "get": a word for reading.
Description, as the server wrote it Get the page where a person buys one specific eSIM plan, for an assistant to hand them a link. The page sells exactly this plan with Apple Pay, Google Pay and card, takes the email at payment, and sends the eSIM there. Nothing is charged or reserved by this call and the buyer needs no account. Use this whenever a PERSON is going to pay. Use create-checkout-session instead when the agent is settling the purchase itself, or for more than one plan or unit.
Annotations the server declares
- title: Get checkout link
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get-destination-infoDetails for one destination: its name and codes, region, how many eSIM plans are sold there, the cheapest and most expensive, the smallest and largest data bundles, and its storefr…No findings
Why it is in this group
- The name "get-destination-info" says "get": a word for reading.
Description, as the server wrote it Details for one destination: its name and codes, region, how many eSIM plans are sold there, the cheapest and most expensive, the smallest and largest data bundles, and its storefront page. Takes a country name ("Japan") or two-letter code ("JP"). Use this to describe a destination before pulling its full plan ladder with list-plans. Whether a plan can be topped up varies by plan and is reported by list-plans, not here.
Annotations the server declares
- title: Get destination info
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get-esim-activationFetch the installable eSIM(s) for a paid order: the QR code image, the LPA activation string, the SM-DP+ address and activation code for manual entry, one-tap install links for iPh…No findings
Why it is in this group
- The name "get-esim-activation" says "get": a word for reading.
Description, as the server wrote it Fetch the installable eSIM(s) for a paid order: the QR code image, the LPA activation string, the SM-DP+ address and activation code for manual entry, one-tap install links for iPhone and Android, and a hosted install page to send the buyer. Identified by the order id together with the email that bought it. Returns an empty esims list while provisioning is still in flight, which normally clears within a minute of payment.
Annotations the server declares
- title: Get eSIM activation details
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get-order-statusCheck an eSIM order after payment: whether it completed and whether its eSIMs have been provisioned yet.No findings
Why it is in this group
- The name "get-order-status" says "get": a word for reading.
Description, as the server wrote it Check an eSIM order after payment: whether it completed and whether its eSIMs have been provisioned yet. Identified by the order id together with the email that bought it, both of which are on the buyer's confirmation email. Provisioning usually finishes within a minute of payment, so an order that is paid but lists no eSIMs yet is normal: check again shortly. Once an eSIM is listed, use get-esim-activation to fetch its QR code and install details.
Annotations the server declares
- title: Get order status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get-planRead everything about one eSIM plan by its id: data allowance, how long it stays valid, what happens after a fair-use cap, whether hotspot and top-ups are supported, the network it…No findings
Why it is in this group
- The name "get-plan" says "get": a word for reading.
Description, as the server wrote it Read everything about one eSIM plan by its id: data allowance, how long it stays valid, what happens after a fair-use cap, whether hotspot and top-ups are supported, the network it runs on, and the retail price in the currency you ask for. Use it to answer a specific question about a plan already found with list-plans or plan-trip, and before buying, to confirm the plan really matches what the traveller asked for. Ask get-plan-coverage instead when the question is which countries it works in. Read-only: it reserves nothing and charges nothing.
Annotations the server declares
- title: Get eSIM plan details
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get-plan-coverageList every country one eSIM plan works in, plus any country of its own region that it leaves out.No findings
Why it is in this group
- The name "get-plan-coverage" says "get": a word for reading.
Description, as the server wrote it List every country one eSIM plan works in, plus any country of its own region that it leaves out. Use it to answer "does this plan also cover Austria?" for a regional or worldwide plan, where the plan name says a region and the traveller needs the actual list. For a single-country plan the answer is that one country. Ask get-plan instead for the data allowance, validity or price. Read-only.
Annotations the server declares
- title: Get plan country coverage
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list-destinationsFind the countries SimFuse sells eSIMs for, with the cheapest plan price ("from" price) for each in the currency you ask for.No findings
Why it is in this group
- The name "list-destinations" says "list": a word for reading.
Description, as the server wrote it Find the countries SimFuse sells eSIMs for, with the cheapest plan price ("from" price) for each in the currency you ask for. Start here when someone names a place: it turns "Portugal" into the two-letter country code the other tools take, and shows what that destination starts at. For one destination, follow it with list-plans; for a trip covering two or more countries, use plan-trip instead. Read-only, and it answers from the SimFuse catalog alone.
Annotations the server declares
- title: List eSIM destinations
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list-plansShow the eSIM plans on sale for one country or region, or search the whole catalog, narrowing by data allowance, validity and price.No findings
Why it is in this group
- The name "list-plans" says "list": a word for reading.
Description, as the server wrote it Show the eSIM plans on sale for one country or region, or search the whole catalog, narrowing by data allowance, validity and price. Use destination with a country code from list-destinations, or region with a slug from list-regions; never both. Use it when the traveller wants to compare what is available or find a plan inside a budget. Prices are live retail prices in the currency you ask for. For a trip covering two or more countries, use plan-trip first: it compares one plan for the whole route against one plan per country and picks the cheapest complete answer. Pass a plan id from here to get-plan, get-plan-coverage or create-checkout-session. Read-only, and it answers from the SimFuse catalog alone.
Annotations the server declares
- title: List eSIM plans
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list-regionsDiscover available eSIM regions, including worldwide scopes, with their canonical slugs, display names, member countries and starting prices.No findings
Why it is in this group
- The name "list-regions" says "list": a word for reading.
Description, as the server wrote it Discover available eSIM regions, including worldwide scopes, with their canonical slugs, display names, member countries and starting prices. Only published regions with active displayed regional plans are listed. Pass a returned region slug to list-plans as region, not destination. Country membership describes the region, not a promise that every plan covers every member: check get-plan-coverage for a specific plan. Read-only; no account or key is needed.
Annotations the server declares
- title: List eSIM regions
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list-topup-optionsData top-ups that can be added to an eSIM the buyer already has, narrowed to what its network will actually accept.No findings
Why it is in this group
- The name "list-topup-options" says "list": a word for reading.
Description, as the server wrote it Data top-ups that can be added to an eSIM the buyer already has, narrowed to what its network will actually accept. Identified by the order id and the email that bought it, plus the ICCID. Read-only: a top-up is bought in the SimFuse app, not through this server, and the response carries the link that opens this eSIM there. Do not pass these package ids to create-checkout-session, which would buy a separate new eSIM rather than add data to this one.
Annotations the server declares
- title: List top-up options
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:20 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://simfuse.app/.well-known/oauth-protected-resource
- Authorization servers
- https://api.simfuse.app
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://simfuse.app/agentic/mcp: tools/list returned 15 tools to an anonymous client, including plan-trip (write), build-plan (write), check-coverage (write), create-checkout-session (write), check-esim-usage (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http esim-storefront https://simfuse.app/agentic/mcpclaude mcp add --transport http esim-storefront https://simfuse.app/agentic/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__esim-storefront__list-destinations",
"mcp__esim-storefront__list-regions",
"mcp__esim-storefront__get-destination-info",
"mcp__esim-storefront__list-plans",
"mcp__esim-storefront__get-plan",
"mcp__esim-storefront__get-plan-coverage",
"mcp__esim-storefront__get-checkout-link",
"mcp__esim-storefront__get-order-status",
"mcp__esim-storefront__get-esim-activation",
"mcp__esim-storefront__list-topup-options"
],
"ask": [
"mcp__esim-storefront__plan-trip",
"mcp__esim-storefront__build-plan",
"mcp__esim-storefront__check-coverage",
"mcp__esim-storefront__create-checkout-session",
"mcp__esim-storefront__check-esim-usage"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as esim-storefront. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/app.simfuse/esim-storefront/verify?hash=aa4fb359b7646fa1ac497005fa289068464ada6edbf218bf6bae2b16f16b7095" | jq -e '.changed == false'Pinned hash aa4fb359b764, from Nov 7, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.simfuse/esim-storefront/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.simfuse/esim-storefront)Source: MCP Registry. Synced Nov 7, 2026, 21:17 UTC.
SimFuse eSIM Storefront MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the SimFuse eSIM Storefront MCP server safe?
- No scan can promise that. What its definitions show: 15 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the SimFuse eSIM Storefront MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the SimFuse eSIM Storefront MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the SimFuse eSIM Storefront MCP server have?
- 15 tools: 5 write, 10 read. plan-trip, build-plan, check-coverage, create-checkout-session, check-esim-usage, list-destinations, list-regions, get-destination-info and 7 more.
Does the SimFuse eSIM Storefront MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the SimFuse eSIM Storefront MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the SimFuse eSIM Storefront MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 7, 2026.