app.iomarkets/topup
REMOTE · IOMARKETS.APP · SCANNED OCT 4
Travel eSIMs and mobile top-ups paid in USDC via x402. A technology demonstration, limited pilot.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1132 tokens (~125/item across 9 items; 9 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 Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "create_pay_link" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 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
How do I install the app.iomarkets/topup MCP server?
app.iomarkets/topup 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
claude mcp add --transport http app-iomarkets-topup 'https://iomarkets.app/mcp'
{
"mcpServers": {
"app-iomarkets-topup": {
"url": "https://iomarkets.app/mcp"
}
}
} {
"servers": {
"app-iomarkets-topup": {
"type": "http",
"url": "https://iomarkets.app/mcp"
}
}
} [mcp_servers.app-iomarkets-topup] url = "https://iomarkets.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-iomarkets-topup": {
"type": "remote",
"url": "https://iomarkets.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-iomarkets-topup --url 'https://iomarkets.app/mcp' --transport streamable-http
mcp_servers:
app-iomarkets-topup:
url: "https://iomarkets.app/mcp" {
"McpServers": {
"app-iomarkets-topup": {
"Transport": "http",
"Url": "https://iomarkets.app/mcp"
}
}
} assistant mcp add app-iomarkets-topup -t streamable-http -u 'https://iomarkets.app/mcp'
{
"mcpServers": {
"app-iomarkets-topup": {
"type": "http",
"url": "https://iomarkets.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 29 Sept 26 +1
- Stability: 0.97 → pass security
- 28 Sept 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
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −1
- Schema quality: pass → fail ▼ functional
- Destructive annotations: pass → 0 functional
- New tool “create_pay_link” functional
- “quote” added an optional parameter “ref” cosmetic
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 6 Oct 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=YE2,O=Let's Encrypt,C=US | 27 Aug 2026 | 25 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5e4bbd499dbd5c9ed743c3c903b6021a14f |
| SANs: iomarkets.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
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. | present | 23684 | 8 | Verified |
| iomarkets.app. | absent | 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 |
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 |
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 →
buy ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| quoteId | string | yes | – |
No output schema declared.
No examples provided.
create_pay_link ~269
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | for range top-up offers: amount in local currency |
| max_uses | integer | – | 0 = reusable until expiry; default 1 for topup, 0 for esim |
| note | string | – | shown on the link page, e.g. 'Your Tokyo trip data' |
| offerId | string | yes | – |
| phone | string | – | topup only: recipient phone, E.164 |
| ref | string | – | your Algorand address, to earn referral share |
| ttl_hours | integer | – | default 168 (7 days) |
| type | string | yes | – |
No output schema declared.
No examples provided.
fx ~73
Indicative USDC → local-currency rate at our sale price, with an estimate for an amount. The quote is the binding price.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | – |
| to | string | yes | ISO-4217, e.g. INR |
| type | string | – | 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 ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | – |
| country | string | – | ISO-3166 alpha-2, e.g. IN |
| limit | integer | – | page size, default 100; 0 means all |
| offset | integer | – | use next_offset from the previous page |
| type | string | yes | payout = 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.
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | E.164, e.g. +919876543210 |
No output schema declared.
No examples provided.
order_status ~52
Check an order. Poll every ~3 s until `terminal` is true: delivered (confirmation + signed receipt), refunded (refund txid + signed receipt) or refund_failed.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | string | yes | – |
No output schema declared.
No examples provided.
quote ~236
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | for range offers: amount in the recipient's local currency |
| fields | object | – | bill-pay / payout recipient fields the offer lists in requiredFields (account_number, bank_code, full_name, vpa, iban…) |
| iccid | string | – | existing eSIM to top up (optional) |
| offerId | string | yes | – |
| payer | string | – | the Algorand address you will pay from (required for payout compliance when this server holds no wallet) |
| phone | string | – | recipient phone for topup/bill (E.164) |
| ref | string | – | referrer's Algorand address — earns a share of margin if the order is delivered (GET /v1/referrals) |
| sender | object | – | payouts only: the principal (legal name + country); reference = partner KYC id, required above $100/day |
| type | string | yes | – |
No output schema declared.
No examples provided.
verify_receipt ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| onChain | boolean | – | confirm the txids on chain; default true |
| orderId | string | – | an order on this service |
| receipt | – | – | a receipt {payload, signature}, or an order response containing one |
No output schema declared.
No examples provided.
What is the app.iomarkets/topup MCP server?
app.iomarkets/topup is an MCP server listed in the public MCP registry as app.iomarkets/topup. Travel eSIMs and mobile top-ups paid in USDC via x402. A technology demonstration, limited pilot. This page covers its hosted endpoint (https://iomarkets.app/mcp).
Is the app.iomarkets/topup MCP server safe to use?
app.iomarkets/topup scores 76 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 app.iomarkets/topup MCP server expose?
app.iomarkets/topup exposes 9 tools: lookup_phone, list_offers, quote, create_pay_link, buy, and 4 more. Their descriptions and schemas cost roughly 1,132 tokens of context every time the server is loaded.
Does the app.iomarkets/topup MCP server require authentication?
No. We connected to app.iomarkets/topup without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the app.iomarkets/topup MCP server still maintained?
app.iomarkets/topup is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.