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

altesim

https://altesim.com

Registry code: ddfd2902272cd9cc

api record

Alt eSIM travel data eSIMs. Start with get_shop_facts. Browse via list_destinations / search_esim_plans / recommend_plans / get_esim_plan. create_checkout (buyer email) returns a Stripe payment link; get_qr_code after pay. Quote only catalog prices (USD). Never invent product URLs.

endpoint
https://altesim.com/api/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 altesim live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is altesim free to use?
Yes — the hub reached it with no key and no payment.
What tools does altesim have?
7 tools: recommend_plans, create_checkout, get_esim_plan, get_qr_code, get_shop_facts, search_esim_plans, list_destinations.
Is altesim 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 99.8%· all time 99.8%

latency
531ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 425 checks · signed record
  • down → live
_ what it is for
used for
  • search travel esim plans
  • get esim plan details
  • create checkout for an esim
  • get esim qr code
takes → gives
text → data, images
tools
4 reads1 moves money
_ 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 7 tools
3 open 4 never probed 3 of 7 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.

  • get_shop_facts open 20h ago

    Shop rules for Alt eSIM in the shop's own words: product model, currency, refund policy, payment/delivery, and how agents must quote prices/URLs. Call this before recommending or buying.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • search_esim_plans reads open 20h ago

    Search Alt eSIM travel data plans. Filter by destination country slug (e.g. 'japan', 'usa', 'europe'), region, and/or max USD price. Returns plans with sku, data amount, validity days, USD price and coverage carriers. All prices are USD.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "region": {
          "enum": [
            "asia",
            "europe",
            "americas",
            "oceania",
            "africa",
            "middle-east"
          ],
          "type": "string",
          "description": "Optional region filter."
        },
        "country": {
          "type": "string",
          "description": "Destination country/region slug, e.g. 'japan', 'south-korea', 'thailand', 'usa', 'europe'. Omit to list all."
        },
        "max_price_usd": {
          "type": "number",
          "description": "Optional max price in USD."
        }
      }
    }
    arguments 25 lines
  • list_destinations reads open 20h ago

    List all Alt eSIM destinations (country/region slugs with English names and region). Use a slug as the 'country' argument for search_esim_plans / recommend_plans.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • recommend_plans unknown never probed

    Recommend up to a few real catalog plans for one destination. Ranks existing SKUs by trip days and usage (light≈0.5 / normal≈1.5 / heavy≈4 GB/day) — never invents prices or URLs. Prefer this for 'what should I buy?'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "country"
      ],
      "properties": {
        "days": {
          "type": "number",
          "description": "Trip length in days (optional). Prefers plans whose validity is close."
        },
        "limit": {
          "type": "number",
          "description": "How many plans to return (1–8, default 3)."
        },
        "usage": {
          "enum": [
            "light",
            "normal",
            "heavy"
          ],
          "type": "string",
          "description": "Data intensity: light≈0.5, normal≈1.5, heavy≈4 GB/day (ranking only)."
        },
        "country": {
          "type": "string",
          "description": "Destination slug, e.g. 'japan', 'thailand', 'europe'."
        },
        "max_price_usd": {
          "type": "number",
          "description": "Optional max USD price filter."
        }
      }
    }
    arguments 33 lines
  • create_checkout moves money unknown never probed

    Create a secure Stripe payment link for an Alt eSIM plan. Returns a payment URL the BUYER opens to pay (the agent never handles card details) AND a checkout_session_id. After the buyer pays, call get_qr_code with that checkout_session_id to fetch the eSIM QR and show it to the buyer. The QR is also emailed. Charged in USD. You MUST collect the buyer's real email.

    mcp-tool

    {
      "type": "object",
      "required": [
        "sku_or_id",
        "email"
      ],
      "properties": {
        "lang": {
          "enum": [
            "en",
            "zh-hk",
            "zh-tw",
            "zh-cn",
            "id",
            "hi",
            "es",
            "fr",
            "nl",
            "ru",
            "uk",
            "kk",
            "uz",
            "pl",
            "cs",
            "hu",
            "ro",
            "de",
            "it",
            "pt",
            "tr",
            "el",
            "ar",
            "ja",
            "ko",
            "th",
            "vi",
            "ms",
            "tl",
            "bn",
            "sv",
            "da",
            "nb",
            "fi",
            "bg",
            "hr",
            "sk",
            "sl",
            "sr",
            "lt",
            "lv",
            "et"
          ],
          "type": "string",
          "description": "Delivery email language (default 'en')."
        },
        "email": {
          "type": "string",
          "description": "Buyer's email — the eSIM QR code is also sent here."
        },
        "sku_or_id": {
          "type": "string",
          "description": "The plan sku or id to buy."
        },
        "customer_code": {
          "type": "string",
          "description": "Optional Alt customer code (format Alt-XXXXXXXX, shown on the buyer's altesim.com account page). If provided, the order is linked to that account and appears in its order history regardless of the delivery email used."
        }
      }
    }
    arguments 69 lines
  • get_esim_plan reads unknown 12h ago

    Get one Alt eSIM plan by its sku or id. Returns full details: title, data amount, validity days, USD price, coverage carriers, product URL.

    mcp-tool

    {
      "type": "object",
      "required": [
        "sku_or_id"
      ],
      "properties": {
        "sku_or_id": {
          "type": "string",
          "description": "The plan sku (e.g. 'eSIM_Alt_JP_1DG1') or id."
        }
      }
    }
    arguments 12 lines
  • get_qr_code reads unknown 12h ago

    Fetch the eSIM QR code(s) for an order, to show the buyer directly. Pass the checkout_session_id from create_checkout. Returns a clear `status`: 'awaiting_payment' (buyer has NOT paid — tell them to pay), 'processing' (paid, eSIM still provisioning — retry in ~30s), 'manual_review' (paid, activation paused for security review; ask buyer to contact [email protected] with the order reference), 'ready' (returns the QR image(s) + ICCID(s) to display), 'expired', 'refunded', or 'failed'. Use the status to tell the buyer exactly what's happening — never assume payment succeeded.

    mcp-tool

    {
      "type": "object",
      "required": [
        "checkout_session_id"
      ],
      "properties": {
        "checkout_session_id": {
          "type": "string",
          "description": "The checkout_session_id from create_checkout (Stripe session id)."
        }
      }
    }
    arguments 12 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 ddfd2902272cd9cc.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ddfd2902272cd9cc/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/ddfd2902272cd9cc/badge.svg)](https://brick.blue/agent/ddfd2902272cd9cc?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
100%

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.