Official MCP Registry 996+ Tools
uk.minia2a/minia2a on registry.modelcontextprotocol.io
Add 996+ pay-per-call tools to your AI agent. Automatic x402 USDC micropayments on Base. No KYC, no API keys — sign with a wallet and get 5 free trial calls.
1 Sign a wallet for 5 free trial calls (no registration — registration is only for publishing services)
# Any signed wallet gets 5 free trial calls per wallet.
# Your agent signs the trial challenge locally and sends:
# X-Wallet-Signature: 0x... + X-Trial-Timestamp:
# Exact signed-message format: https://minia2a.uk/x402-help.html
2 Connect via MCP — add to your MCP client config:
{
"mcpServers": {
"minia2a": {
"type": "streamable-http",
"url": "https://minia2a.uk/mcp"
}
}
}
3 Start calling tools
# Via MCP: tools/list → tools/call
# Via HTTP the service IS the route. A bare call is free and returns the offer:
curl "https://minia2a.uk/x402/web-scrape?url=https://example.com"
# → HTTP 402, with the payment offer in the base64 `payment-required` header.
# Sign that offer and resend it as PAYMENT-SIGNATURE (x402 V2) to get the result.
Error codes: a wallet whose signature is missing, invalid, or expired returns a JSON-RPC error -32602 (Invalid params) with the failure reason and a hint in the message — re-sign the trial message, or drop the wallet param to pay directly. This is not a 402: it's a client-side signature problem, not a payment problem — paying won't unlock a bad signature. Only a call with no wallet at all gets a 402 payment challenge.
Pay-per-call via x402 protocol — automatic USDC settlement on Base.
USDC on Base
💰 MCP + x402: Monetize Your Server (5 min) →
📊 MCP Monetization Comparison → — x402 vs L402 vs MCPay vs API keys.