_ registry / mcp streamable-http · checked 13h ago

simowl-esim

https://simowl.com

Registry code: 6598c97cceb84a97

api record

SimOwl sells prepaid, data-only travel eSIMs. Typical flow: estimate_trip_data for the trip length, find_esim_plans for the destination (with min_data_gb / min_days), optionally check_phone_esim_support, then give the person the buy_url of the chosen plan. You cannot buy for the person: they enter their email and pay on the page. Prices include taxes.

endpoint
https://simowl.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is simowl-esim live?
Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
Is simowl-esim free to use?
Yes — the hub reached it with no key and no payment.
What tools does simowl-esim have?
4 tools: check_phone_esim_support, estimate_trip_data, find_esim_plans, list_esim_destinations.
Is simowl-esim safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
470ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_esim_destinations open 13h ago

    Every country and multi-country region SimOwl sells travel eSIMs for, with the lowest price and the page URL.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "currency": {
          "type": "string",
          "description": "ISO 4217 code to quote prices in (USD, EUR, GBP, JPY...). Defaults to EUR when not sold."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • check_phone_esim_support unknown 13h ago

    Whether a phone model supports eSIM: "iPhone 13", "Galaxy S23", "Pixel 7a", or an Android model code such as "SM-S911B". Returns supported, not_supported or unknown.

    mcp-tool

    {
      "type": "object",
      "required": [
        "model"
      ],
      "properties": {
        "model": {
          "type": "string",
          "description": "Phone model name or code."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • estimate_trip_data unknown 40h ago

    How much mobile data a trip needs, and the plan size to pick, for light, typical or heavy use.

    mcp-tool

    {
      "type": "object",
      "required": [
        "days"
      ],
      "properties": {
        "days": {
          "type": "number",
          "description": "Trip length in days (1-365)."
        },
        "profile": {
          "enum": [
            "light",
            "typical",
            "heavy"
          ],
          "type": "string",
          "description": "light: maps and messaging; typical: plus social, music, a little video; heavy: HD video, hotspot."
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • find_esim_plans unknown 13h ago

    Prepaid data-only travel eSIM plans from SimOwl for a country or region, cheapest first, with prices and a buy_url. Includes regional plans that also cover the country. Give the person the buy_url of the plan they choose: the plan opens already selected, they enter their email and pay; the QR code arrives by email within minutes.

    mcp-tool

    {
      "type": "object",
      "required": [
        "destination"
      ],
      "properties": {
        "limit": {
          "type": "number",
          "description": "Max plans to return (default 30, max 100)."
        },
        "currency": {
          "type": "string",
          "description": "ISO 4217 code to quote prices in (USD, EUR, GBP, JPY...). Defaults to EUR when not sold."
        },
        "min_days": {
          "type": "number",
          "description": "Only plans valid for at least this many days (trip length)."
        },
        "destination": {
          "type": "string",
          "description": "Country name or ISO 3166-1 alpha-2 code (\"Japan\", \"JP\"), or a region (\"Europe\", \"Asia Pacific\")."
        },
        "min_data_gb": {
          "type": "number",
          "description": "Only plans with at least this much data (unlimited plans always match)."
        },
        "unlimited_only": {
          "type": "boolean",
          "description": "Only unlimited-data plans."
        }
      },
      "additionalProperties": false
    }
    arguments 33 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 6598c97cceb84a97.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6598c97cceb84a97/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6598c97cceb84a97/badge.svg)](https://brick.blue/agent/6598c97cceb84a97?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.