Skip to content

eSIM SOS MCP server

net.esimsos/esimsosesimsos.netstreamable-httpv1.0.0Scanned

Find travel eSIM plans, compare prices and create an order the user pays by link.

6 tools: 2 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 2 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 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.
Govern this server →

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 eSIM SOS MCP server can do

The eSIM SOS MCP server is published by esimsos.net, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: create_order and install_instructions), but cannot delete data. 4 tools only read.

2 tools bring in text other people can write (compare_prices and create_order).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.0.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.

6 tools

Changes things 2Claude Code: ask
  • create_orderCreate an unpaid eSIM order and get a payment link.Reads text others writeNo findings

    Why it is in this group

    • The name "create_order" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Create an unpaid eSIM order and get a payment link. Payment is always done by the human: give the user the payment link, never try to pay yourself and never ask for card details. Ask the user for their email first: the eSIM QR code is sent there. Creates a real order, so call it only after the user picked the plan.

    Annotations the server declares

    • title: Create order (returns payment link)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • install_instructionsAfter payment: link to the order page with the QR code and step-by-step eSIM install instructions for iPhone and Android.1 finding

    Why it is in this group

    • The name "install_instructions" says "install": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "install_instructions" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "install_instructions" says "install": a word for a change.

      What this check looks for
    Description, as the server wrote it
    After payment: link to the order page with the QR code and step-by-step eSIM install instructions for iPhone and Android. Requires order_id and email.

    Annotations the server declares

    • title: Install instructions
    • readOnlyHint: true
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • compare_pricesCompare eSIM prices of several providers for a country and data size using the open esimdar.com dataset (CC BY 4.0).Reads text others writeNo findings

    Why it is in this group

    • The name "compare_prices" says "compare": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Compare eSIM prices of several providers for a country and data size using the open esimdar.com dataset (CC BY 4.0). Disclosure: esimdar.com is owned and run by eSIM SOS, the shop behind this server; eSIM SOS is listed as an ordinary row. Tell the user about this ownership and present the results neutrally.

    Annotations the server declares

    • title: Compare eSIM prices
    • readOnlyHint: true
    • openWorldHint: true
  • list_plansList eSIM data plans for a country with final prices in RUB (one price for every payment method).No findings

    Why it is in this group

    • The name "list_plans" says "list": a word for reading.
    Description, as the server wrote it
    List eSIM data plans for a country with final prices in RUB (one price for every payment method). Local plans first, then regional ones.

    Annotations the server declares

    • title: List eSIM plans
    • readOnlyHint: true
    • openWorldHint: false
  • order_statusCheck the payment and delivery status of an order.No findings

    Why it is in this group

    • The name "order_status" says "status": a word for reading.
    Description, as the server wrote it
    Check the payment and delivery status of an order. Requires both order_id and the email used for the order.

    Annotations the server declares

    • title: Order status
    • readOnlyHint: true
    • openWorldHint: false
  • search_destinationsFind a travel destination (country) sold by eSIM SOS by name in English or Russian, or by ISO code.No findings

    Why it is in this group

    • The name "search_destinations" says "search": a word for reading.
    Description, as the server wrote it
    Find a travel destination (country) sold by eSIM SOS by name in English or Russian, or by ISO code. Returns country codes for list_plans.

    Annotations the server declares

    • title: Search destinations
    • readOnlyHint: 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 outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:16 UTC, unchanged since Oct 22, 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
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://esimsos.net/api/mcp: tools/list returned 6 tools to an anonymous client, including create_order (write), install_instructions (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "install_instructions" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "install_instructions" says "install": a word for a change.

    What this check looks for

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.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http esimsos https://esimsos.net/api/mcp
claude mcp add --transport http esimsos https://esimsos.net/api/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__esimsos__search_destinations",
      "mcp__esimsos__list_plans",
      "mcp__esimsos__compare_prices",
      "mcp__esimsos__order_status"
    ],
    "ask": [
      "mcp__esimsos__create_order",
      "mcp__esimsos__install_instructions"
    ],
    "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 esimsos. Review it before you use it.

Capability tags behind 2 rules
  • mcp__esimsos__compare_prices untrusted-input
  • mcp__esimsos__create_order untrusted-input

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/net.esimsos/esimsos/verify?hash=cdd81abb5b3ff154a786721e23b8ccc5a60d7c570f4e36084ed8fd5ec733080b" | jq -e '.changed == false'

Pinned hash cdd81abb5b3f, from Nov 18, 2026, 00:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/net.esimsos/esimsos/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for net.esimsos/esimsos
[![Anlyon Radar](https://radar.anlyon.com/badge/net.esimsos/esimsos.svg)](https://radar.anlyon.com/servers/net.esimsos/esimsos)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:53 UTC.

eSIM SOS MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the eSIM SOS MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the eSIM SOS MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the eSIM SOS 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 eSIM SOS MCP server have?

6 tools: 2 write, 4 read. create_order, install_instructions, search_destinations, list_plans, compare_prices and order_status.

Does the eSIM SOS MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the eSIM SOS MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the eSIM SOS MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.