# app.iomarkets/topup (remote · iomarkets.app)

Travel eSIMs and mobile top-ups paid in USDC via x402. A technology demonstration, limited pilot.

- Trust score: 76/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `iomarkets.app`: 76/100 (this document), [markdown](https://verifymcp.io/servers/app-iomarkets-topup/iomarkets.md), [page](https://verifymcp.io/servers/app-iomarkets-topup/iomarkets)

## Channel facts

- Endpoint: `https://iomarkets.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.8`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 74% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http app-iomarkets-topup 'https://iomarkets.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-iomarkets-topup": {
      "url": "https://iomarkets.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-iomarkets-topup": {
      "type": "http",
      "url": "https://iomarkets.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-iomarkets-topup]
url = "https://iomarkets.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-iomarkets-topup": {
      "type": "remote",
      "url": "https://iomarkets.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-iomarkets-topup --url 'https://iomarkets.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-iomarkets-topup:
    url: "https://iomarkets.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-iomarkets-topup": {
      "Transport": "http",
      "Url": "https://iomarkets.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-iomarkets-topup -t streamable-http -u 'https://iomarkets.app/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-29 (score 76, +1)

- [security] Stability: 0.97 → pass

### 2026-09-28 (score 75, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 75, +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.

### 2026-09-25 (score 74, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 73, +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.

### 2026-09-21 (score 72, +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.

### 2026-09-19 (score 71, +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.

### 2026-09-16 (score 70, −1)

- [functional regression] Schema quality: pass → fail
- [functional] Destructive annotations: pass → 0
- [functional] New tool “create_pay_link”
- [cosmetic] “quote” added an optional parameter “ref”

## MCP tools (9)

### `lookup_phone` (~137 tokens)

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.

Input parameters:

- `phone` (string, required): E.164, e.g. +919876543210

### `list_offers` (~133 tokens)

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.

Input parameters:

- `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, required): payout = international payment (bank / mobile money / UPI)

### `quote` (~236 tokens)

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.

Input parameters:

- `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, required)
- `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, required)

### `create_pay_link` (~269 tokens)

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.

Input parameters:

- `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, required)
- `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, required)

### `buy` (~84 tokens)

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.

Input parameters:

- `quoteId` (string, required)

### `order_status` (~52 tokens)

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

Input parameters:

- `orderId` (string, required)

### `verify_receipt` (~123 tokens)

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.

Input parameters:

- `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

### `fx` (~73 tokens)

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

Input parameters:

- `amount` (number)
- `to` (string, required): ISO-4217, e.g. INR
- `type` (string): what the rate is for; default payout

### `ledger` (~25 tokens)

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-iomarkets-topup/iomarkets#diagnostics

## Score history

- 2026-10-04: 76
- 2026-10-03: 76
- 2026-10-02: 76
- 2026-10-01: 76
- 2026-09-30: 76
- 2026-09-29: 76
- 2026-09-28: 75
- 2026-09-27: 75
- 2026-09-26: 74
- 2026-09-25: 74
- 2026-09-24: 73
- 2026-09-23: 73
- 2026-09-22: 72
- 2026-09-21: 72
- 2026-09-20: 71
- 2026-09-19: 71
- 2026-09-18: 70
- 2026-09-17: 70
- 2026-09-16: 70
- 2026-09-15: 71
- 2026-09-14: 71
- 2026-09-13: 71
- 2026-09-12: 70
- 2026-09-11: 70
- 2026-09-10: 69
- 2026-09-09: 69
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 67
- 2026-09-05: 67

## Common questions

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

## Links

- Remote endpoint: https://iomarkets.app/mcp
- Website: https://iomarkets.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-iomarkets-topup/iomarkets.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-iomarkets-topup/iomarkets.json
- HTML version of this page: https://verifymcp.io/servers/app-iomarkets-topup/iomarkets