Is the Iomarkets Topup MCP server down?

mcp-registry/app.iomarkets/topup · v0.1.0

healthy
Last checked 2026-10-24 07:10 UTC · handshake 638ms

As of 2026-10-24 07:10 UTC, the Iomarkets Topup MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
100%
checks observed
4,578
outages (90d)
5
tools
11

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

Install Iomarkets Topup MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http iomarkets-topup-mcp-server https://iomarkets.app/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "iomarkets-topup-mcp-server": {
      "type": "http",
      "url": "https://iomarkets.app/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (67/100)

D (67/100): 0 error(s), 5 warning(s) across 11 tool(s); ~2,334 tokens of tool definitions.
Scores higher than 2% of 15,626 MCP servers Glimind has audited.
Its tool list costs an agent ~2,334 tokens per session — more than 50% of servers.
66 → 67 since 2026-10-17
no tool-poisoning patterns
Schemas85
Descriptions45
Safety hints5
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (6)

11 of 11 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: buy, create_pay_link, fx, ledger, list_offers and 6 more

9 parameter(s) across 7 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: buy, create_pay_link, fx, list_offers, order_status and 2 more

2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: buy, create_pay_link

1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: verify_receipt

Handshake + tools/list takes ~1,891 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 6 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 7 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fapp.iomarkets%2Ftopup/fixes

buy 1 change
{
  "name": "buy",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "quoteId"
    ],
    "properties": {
      "quoteId": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
create_pay_link 1 change
{
  "name": "create_pay_link",
  "description": "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 sh",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "type",
      "offerId"
    ],
    "properties": {
      "ref": {
        "type": "string",
        "description": "your Algorand address, to earn referral share"
      },
      "note": {
        "type": "string",
        "maxLength": 140,
        "description": "shown on the link page, e.g. 'Your Tokyo trip data'"
      },
      "type": {
        "enum": [
          "topup",
          "esim"
        ],
        "type": "string"
      },
      "phone": {
        "type": "string",
        "description": "topup only: recipient phone, E.164"
      },
      "amount": {
        "type": "number",
        "description": "for range top-up offers: amount in local currency",
        "exclusiveMinimum": 0
      },
      "offerId": {
        "type": "string"
      },
      "max_uses": {
        "type": "integer",
        "maximum": 1000,
        "minimum": 0,
        "description": "0 = reusable until expiry; default 1 for topup, 0 for esim"
      },
      "ttl_hours": {
        "type": "integer",
        "maximum": 720,
        "minimum": 1,
        "description": "default 168 (7 days)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
list_offers 1 change
{
  "name": "list_offers",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "type"
    ],
    "properties": {
      "type": {
        "enum": [
          "topup",
          "esim",
          "bill",
          "payout"
        ],
        "type": "string",
        "description": "payout = international payment (bank / mobile money / UPI)"
      },
      "brand": {
        "type": "string"
      },
      "limit": {
        "type": "integer",
        "maximum": 500,
        "minimum": 0,
        "description": "page size, default 100; 0 means all"
      },
      "offset": {
        "type": "integer",
        "maximum": 9007199254740991,
        "minimum": 0,
        "description": "use next_offset from the previous page"
      },
      "country": {
        "type": "string",
        "maxLength": 2,
        "minLength": 2,
        "description": "ISO-3166 alpha-2, e.g. IN"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/app.iomarkets/topup"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/app.iomarkets/topup"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.iomarkets%2Ftopup.svg)](https://glimind.com/server/mcp-registry%2Fapp.iomarkets%2Ftopup?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fapp.iomarkets%2Ftopup?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.iomarkets%2Ftopup.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.iomarkets%2Ftopup.svg
   :target: https://glimind.com/server/mcp-registry%2Fapp.iomarkets%2Ftopup?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:fb2c7fa372393394…, first seen 2026-10-21, included at leaf 41520 of 57,189. Version history · verify what your client received.

Tools (11)

Compare: most reliable payments servers · most reliable finance servers · most reliable data servers · most reliable communication servers · most reliable security servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Iomarkets Topup MCP server down right now?

As of 2026-10-24 07:10 UTC, the Iomarkets Topup MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Iomarkets Topup MCP server provide?

Iomarkets Topup MCP server advertises 11 tools, including buy, create_pay_link, fx, ledger, list_offers.

How do I install Iomarkets Topup MCP server?

Point your MCP client at this streamable-http endpoint: https://iomarkets.app/mcp

Is the Iomarkets Topup MCP server safe to connect to an AI agent?

Glimind scanned all 11 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Iomarkets Topup MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve