mcpbeat

Micropay Test Suite MCP Server

app.netlify.micropay-test-suite/micropay-test-suite
answering

Micropay Test Suite is answering right now. Last checked 8 min ago. It exposes 1 tools.

Verify your agent's x402 payment flow for free on Base Sepolia testnet before real money moves.

Uptime history 44 hours of history
44 hours agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
732 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add micropay-test-suite --transport http https://micropay-test-suite.netlify.app/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "micropay-test-suite": {
      "url": "https://micropay-test-suite.netlify.app/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.micropay-test-suite]
url = "https://micropay-test-suite.netlify.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "micropay-test-suite": {
      "url": "https://micropay-test-suite.netlify.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "micropay-test-suite": {
      "url": "https://micropay-test-suite.netlify.app/api/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

payment
check_payment_flow
Verifies an agent's x402 payment flow against a free Base Sepolia testnet endpoint. Call with no arguments first to get back the payment-required challenge (price, network, payTo). Sign it with your x402 client, then call again passing paymentSignature as the encoded PAYMENT-SIGNATURE header value to get back a verified/failed receipt.

Endpoints

URLTransportStateLatencyChecked
https://micropay-test-suite.netlify.app/api/mcp streamable-http answering 491 ms 8 min ago

Micropay Test Suite — questions

Answers built from our own checks of this server.

What can Micropay Test Suite do?
It exposes 1 tools, read directly from the server on our last check. Among them: check_payment_flow. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Micropay Test Suite working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 732 ms. The bar chart above shows every period we have measured.
How do I connect Micropay Test Suite?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Micropay Test Suite need an API key?
No. Micropay Test Suite completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Micropay Test Suite?
It answers our handshake in 732 ms on average, which is faster than 11% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.