Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

IoMarkets Topup (demo)

REMOTE · IOMARKETS.APP

Demo only, payments switched off. Travel eSIMs and mobile top-ups priced in USDC via x402.

Available components

0 this week 86 Trust /100

Last scanned (15 hours ago)

Scores higher than 88% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1692 tokens (~153/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
    • Tool “buy” rewrote its description, which is the text the model reads security
    • Tool “create_pay_link” rewrote its description, which is the text the model reads security
    • Tool “quote” rewrote its description, which is the text the model reads security
    • Tool “quote_vouchers” rewrote its description, which is the text the model reads security
    • Schema quality: excellent → good functional
  • 7 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Oct 26 0
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 29 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 27 Oct 26 +12
    • Authorization: unverified → partial ▲ security
    • HSTS header: fail → pass ▲ security
    • Tool coverage: 75% → 100% ▲ functional
    • Schema quality: good → excellent functional
    • Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
    • “buy” reworded the description of “quoteId” cosmetic
    • “create_pay_link” reworded the description of “offerId” cosmetic
    • “create_pay_link” reworded the description of “type” cosmetic
    • “fx” reworded the description of “amount” cosmetic
    • “list_offers” reworded the description of “brand” cosmetic
    • “order_status” reworded the description of “orderId” cosmetic
    • “quote” reworded the description of “offerId” cosmetic
    • “quote” reworded the description of “type” cosmetic
    • “voucher_batch” reworded the description of “batchId” cosmetic
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://iomarkets.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=iomarkets.app CN=WE1,O=Google Trust Services,C=US 25 Oct 2026 23 Jan 2027 ECDSA 256 ECDSA-SHA256 381ecac8a82b169413f4b87d4080b806
SANs: iomarkets.app, *.iomarkets.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of iomarkets.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
iomarkets.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
content-security-policy frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy same-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://iomarkets.app/mcp Verified 200
http (plaintext) http://iomarkets.app/mcp HTTPS enforced 308 https://iomarkets.app/mcp
MCP tools · 11 exposed · ~1,692 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
buy ~149

Demo only: payments are switched off, so this answers with an error and nothing can be bought. Get the x402 payment challenge for a quote. This hosted server holds no wallet, so it does NOT spend your money: it returns the exact amount, asset, payTo address and facilitator for you to pay from your own Algorand wallet, then you POST the quote again with your payment signature. Requires prior human confirmation of the quote. Works the same for a quote from quote_vouchers; the paid response is the batch (batchId and claim links) rather than an order.

NameTypeReqDescription
quoteIdstringyesthe quoteId returned by quote or quote_vouchers, after the human confirmed it

No output schema declared.

No examples provided.

create_pay_link ~320

Demo only: payments are switched off, so this answers with an error and nothing can be bought. Create a checkout link a HUMAN pays from their own Algorand wallet (Pera). Use this when you have no wallet, or when the person should approve and pay themselves: they open the link, see the exact price, sign in their wallet, and the result (the eSIM QR code, or the top-up confirmation) appears on the page. You never hold a key. A top-up link can be paid by anyone — send it to family as 'top up my phone'. An eSIM link delivers to whoever pays. Free. Add `ref` (your Algorand address) to earn a share of margin on each delivered order.

NameTypeReqDescription
amountnumber–for range top-up offers: amount in local currency
max_usesinteger–0 = reusable until expiry; default 1 for topup, 0 for esim
notestring–shown on the link page, e.g. 'Your Tokyo trip data'
offerIdstringyesthe offer's offerId from list_offers or lookup_phone, e.g. ea-JC063
phonestring–topup only: recipient phone, E.164
refstring–your Algorand address, to earn referral share
ttl_hoursinteger–default 168 (7 days)
typestringyesthe offer's type, as list_offers returned it

No output schema declared.

No examples provided.

fx ~95

Indicative USDC → local-currency rate at our sale price, with an estimate for an amount. The quote is the binding price.

NameTypeReqDescription
amountnumber–an amount in the local currency `to`, to estimate its USDC price, e.g. 5000
tostringyesISO-4217, e.g. INR
typestring–what the rate is for; default payout

No output schema declared.

No examples provided.

ledger ~25

Public delivery ledger: totals, delivered-or-refunded %, volume, countries, recent orders.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_offers ~150

Browse purchasable offers: mobile top-ups, travel eSIMs, prepaid bills, or international payment corridors (bank / mobile money / UPI) for a country. Free. Prices shown are indicative; the quote fixes them.

NameTypeReqDescription
brandstring–operator or provider brand to filter by, as list_offers returns it in `brand`
countrystring–ISO-3166 alpha-2, e.g. IN
limitinteger–page size, default 100; 0 means all
offsetinteger–use next_offset from the previous page
typestringyespayout = international payment (bank / mobile money / UPI)

No output schema declared.

No examples provided.

lookup_phone ~137

Identify the country and mobile operator of a phone number and list the top-up offers available for it. Free. The operator is DETECTED from the number range and is a guess: MVNOs (Tesco Mobile, Giff Gaff, Lebara, Voxi, Sky…) resolve to the host network they ride on. Read the detected brand back to the human and have them confirm it before buying, and use `other_brands` to correct it — a voucher bought for the wrong network delivers successfully and cannot be redeemed or refunded.

NameTypeReqDescription
phonestringyesE.164, e.g. +919876543210

No output schema declared.

No examples provided.

order_status ~58

Check an order. Poll every ~3 s until `terminal` is true: delivered (confirmation + signed receipt), refunded (refund txid + signed receipt) or refund_failed.

NameTypeReqDescription
orderIdstringyesthe orderId returned by buy

No output schema declared.

No examples provided.

quote ~287

Demo only: payments are switched off, so this answers with an error and nothing can be bought. Lock a price (10 minutes) for one purchase. Returns quoteId, exact USDC price and what will be delivered. Free. ALWAYS show the human the price and the recipient before buying.

NameTypeReqDescription
amountnumber–for range offers: amount in the recipient's local currency
fieldsobject–bill-pay / payout recipient fields the offer lists in requiredFields (account_number, bank_code, full_name, vpa, iban…)
iccidstring–existing eSIM to top up (optional)
offerIdstringyesthe offer's offerId from list_offers or lookup_phone, e.g. ea-JC063
payerstring–the Algorand address you will pay from (required for payout compliance when this server holds no wallet)
phonestring–recipient phone for topup/bill (E.164)
refstring–referrer's Algorand address — earns a share of margin if the order is delivered (GET /v1/referrals)
senderobject–payouts only: the principal (legal name + country); reference = partner KYC id, required above $100/day
typestringyesthe offer's type, as list_offers returned it

No output schema declared.

No examples provided.

quote_vouchers ~257

Demo only: payments are switched off, so this answers with an error and nothing can be bought. Lock a price (10 minutes) for a BATCH of travel eSIMs paid in one payment: N claim links, one per person, for a group trip, a conference delegation or event giveaways. Each eSIM is bought when its link is claimed (the person opens it on their phone and installs the QR), and links nobody claims within 30 days are refunded to the paying wallet. Free. Pay the returned quoteId with `buy`, or send the human to this service's /pay/?mode=vouchers page to buy it with their own wallet. Limits: 2–50 eSIMs, each within the per-order limit, the batch within its own limit ($100 by default). ALWAYS show the human the total and the count before buying.

NameTypeReqDescription
countintegeryeshow many eSIMs, i.e. claim links
notestring–shown on every claim page, e.g. 'Devcon 8 delegation'
offerIdstringyesan esim offer from list_offers type=esim
payerstring–the Algorand address you will pay from

No output schema declared.

No examples provided.

verify_receipt ~125

Verify an ed25519-signed receipt: the signature, and — unless you pass onChain:false — both txids against an Algorand indexer. Give it an orderId to check one of this service's own orders, or a receipt object to check ANY receipt in this format, including one issued by another server.

NameTypeReqDescription
onChainboolean–confirm the txids on chain; default true
orderIdstring–an order on this service
receiptobject–a receipt {payload, signature}, or an order response containing one

No output schema declared.

No examples provided.

voucher_batch ~89

A paid voucher batch: every claim link, which have been claimed and delivered, the expiry, and any refund for unclaimed links. The batchId is the only handle on the links — keep it, and hand each person their own link privately (whoever opens a link first gets that eSIM).

NameTypeReqDescription
batchIdstringyesthe batchId returned by buy for a quote_vouchers quote

No output schema declared.

No examples provided.

Install

How do I install the IoMarkets Topup (demo) MCP server?

IoMarkets Topup (demo) is a hosted endpoint at https://iomarkets.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · iomarkets.app

# add to Claude Code
claude mcp add --transport http app-iomarkets-topup 'https://iomarkets.app/mcp'
Common questions

What is the IoMarkets Topup (demo) MCP server?

IoMarkets Topup (demo) is an MCP server listed in the public MCP registry as app.iomarkets/topup. Demo only, payments switched off. Travel eSIMs and mobile top-ups priced in USDC via x402. This page covers its hosted endpoint (https://iomarkets.app/mcp).

Is the IoMarkets Topup (demo) MCP server safe to use?

IoMarkets Topup (demo) scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the IoMarkets Topup (demo) MCP server expose?

IoMarkets Topup (demo) exposes 11 tools: lookup_phone, list_offers, quote, create_pay_link, buy, and 6 more. Their descriptions and schemas cost roughly 1,692 tokens of context every time the server is loaded.

Does the IoMarkets Topup (demo) MCP server require authentication?

No. We connected to IoMarkets Topup (demo) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the IoMarkets Topup (demo) MCP server still maintained?

IoMarkets Topup (demo) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the IoMarkets Topup (demo) MCP server?

VerifyMCP ran 13 checks on IoMarkets Topup (demo), covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.