x402 Micropayments MCP - buyer/seller automation, quota/pro tier, Drive evidence
x402 Micropayments MCP - buyer/seller automation, quota/pro tier, Drive evidence harness
active Production-safe Score 91/100 http no auth
At a glance
| Endpoint | https://x402-mcp.onrender.com/mcp/mcp |
|---|---|
| Source | https://github.com/kwizzlesurp10-ctrl/x402-mcp |
| Transport | http |
| Tools | 21 |
| Auth | none |
| First seen | 2026-08-21 19:30:28 |
| Last checked | 2026-11-17 21:49:28 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 719 / 1105 ms |
| Last successful check | 2026-11-17 21:49:28 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (21)
x402.agent_card— Return the A2A Protocol v1.0 Agent ID Card and MCP server card. Optional target_id filters to a skill id, name, or tag.x402.discover— Discover paid HTTP APIs in the x402 Bazaar via the facilitator catalog. Call this first to find a resource URL, then x402.probe and x402.payx402.probe— Probe a URL for HTTP 402 PAYMENT-REQUIRED terms using the x402 client SDK. Use before x402.pay_and_fetch to inspect price, network, and payTx402.pay_and_fetch— Pay USDC via x402 and fetch a protected HTTP resource in one call. Requires EVM_PRIVATE_KEY on this host; otherwise use x402.probe for a no-x402.build_seller— Build seller-side x402 payment requirements for your own HTTP resource. Pass resource_url plus discovery_* fields to catalog the endpoint inx402.verify— Verify an x402 PAYMENT-SIGNATURE against PAYMENT-REQUIRED terms via the facilitator. Call after a buyer presents a signature and before relex402.policy_check— Decode a caller-supplied merchant PAYMENT-REQUIRED header and evaluate each accepts[] option against an explicit buyer policy (networks, payx402.networks— List supported settlement networks, facilitators, and x402 v2 header names. Call when choosing a preferred_network for x402.pay_and_fetch orcommerce.pro_requirements— Build x402 payment requirements to purchase the Pro quota tier. Next: pay those terms, then commerce.activate_pro with the signature.commerce.activate_pro— Verify a Pro-tier x402 payment and unlock Pro quota limits for the agent. MCP-native: call without payment to receive x402 requirements in tcommerce.credits_requirements— Build x402 payment requirements to buy a pack of per-use MCP tool credits. Next: pay those terms, then commerce.purchase_credits with the sicommerce.purchase_credits— Verify an x402 payment and add per-use tool credits to the agent. MCP-native: call without payment for x402 requirements, then retry with _mswarm.research— Run the swarm agency: compose a research product from free inputs and list it for resale. Pass allow_paid_inputs=true only when buying upstrswarm.settle— Verify and settle a buyer's x402 payment for a listed composite product and record revenue. Call with product_id plus PAYMENT-SIGNATURE afteswarm.revenue— Get swarm composite economics: spend, composite sales, LTV:CAC, margins, per-source scores. total_revenue_usdc is swarm listings only; storepulse.base— Get live Base Network Pulse: base fee, EIP-1559 projection, utilization, USD settlement cost, verdict. Call before settling on Base when youops.metrics— Get host OS telemetry: CPU, memory, swap, disk, network, and an ok/warn/critical health verdict. Call to diagnose this MCP host; set includecity.list— List US cities with paid_url and free sample_url for property compliance. Start here — each paid lookup is $0.01 USDC and returns a normalizcity.sample— Free fixed-address preview of paid property-check JSON (verdict, summary, schema). Use before city.check to validate parsing without spendincity.check— Is this US address licensed / flagged / showing open violations? One city.check ($0.01 USDC, x402 on Base) returns verdict, summary, dates,a2a.resolve_card— Discover and inspect an external Agent-to-Agent (A2A) node by domain or URL. Fetches .well-known/agent-card.json, validates protocol compati
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:49:28 | ✓ | ✓ | 578 ms | 90 | active |
| 2026-11-17 21:34:19 | ✓ | ✓ | 503 ms | 90 | active |
| 2026-11-17 21:19:10 | ✓ | ✓ | 948 ms | 90 | active |
| 2026-11-17 21:04:03 | ✓ | ✓ | 801 ms | 90 | active |
| 2026-11-17 20:48:43 | ✓ | ✓ | 592 ms | 90 | active |
| 2026-11-17 20:33:39 | ✓ | ✓ | 667 ms | 90 | active |
| 2026-11-17 20:18:38 | ✓ | ✓ | 885 ms | 90 | active |
| 2026-11-17 20:03:09 | ✓ | ✓ | 742 ms | 90 | active |
| 2026-11-17 19:47:40 | ✓ | ✓ | 590 ms | 90 | active |
| 2026-11-17 19:32:35 | ✓ | ✓ | 697 ms | 90 | active |
| 2026-11-17 19:17:29 | ✓ | ✓ | 633 ms | 90 | active |
| 2026-11-17 19:01:54 | ✓ | ✓ | 1198 ms | 86 | active |
| 2026-11-17 18:46:48 | ✓ | ✓ | 662 ms | 90 | active |
| 2026-11-17 18:31:46 | ✓ | ✓ | 642 ms | 90 | active |
| 2026-11-17 18:16:45 | ✓ | ✓ | 688 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://x402-mcp.onrender.com/mcp/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/x402-mcp-onrender-com-mcp-mcp # JSON