x402 Micropayments MCP

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Law & government data

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://x402-mcp.onrender.com/mcp/mcp

claude mcp add --transport http x402 https://x402-mcp.onrender.com/mcp/mcp

{
  "mcpServers": {
    "x402": {
      "url": "https://x402-mcp.onrender.com/mcp/mcp"
    }
  }
}

{
  "servers": {
    "x402": {
      "type": "http",
      "url": "https://x402-mcp.onrender.com/mcp/mcp"
    }
  }
}

https://x402-mcp.onrender.com/mcp/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.

• 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.pay_and_fetch.

• x402.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 payTo without spending.

• x402.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-spend 402.

• x402.build_seller

  Build seller-side x402 payment requirements for your own HTTP resource. Pass resource_url plus discovery_* fields to catalog the endpoint in Bazaar.

• x402.verify

  Verify an x402 PAYMENT-SIGNATURE against PAYMENT-REQUIRED terms via the facilitator. Call after a buyer presents a signature and before releasing paid content.

• x402.policy_check

  Decode a caller-supplied merchant PAYMENT-REQUIRED header and evaluate each accepts[] option against an explicit buyer policy (networks, pay_to, assets, max atomic amount). Does not fetch merchant URLs or settle the inspected purchase. Unpaid → PaymentRequired for this server's a

• x402.networks

  List supported settlement networks, facilitators, and x402 v2 header names. Call when choosing a preferred_network for x402.pay_and_fetch or x402.build_seller.

• commerce.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 the tool result, then retry with _meta['x402/payment'] (@x402/mcp client). Legacy: pass PAYMENT-SIGNATURE + PAYMENT-REQUIRED after commerce.p

• commerce.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 signature.

• commerce.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 _meta['x402/payment']. Legacy: PAYMENT-SIGNATURE + PAYMENT-REQUIRED after commerce.credits_requirements.

• swarm.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 upstream x402 services is intended.

• swarm.settle

  Verify and settle a buyer's x402 payment for a listed composite product and record revenue. Call with product_id plus PAYMENT-SIGNATURE after the buyer pays.

• swarm.revenue

  Get swarm composite economics: spend, composite sales, LTV:CAC, margins, per-source scores. total_revenue_usdc is swarm listings only; storefront.revenue_usdc is the full settled ledger. Call after swarm.research or swarm.settle to inspect realized economics.

• pulse.base

  Get live Base Network Pulse: base fee, EIP-1559 projection, utilization, USD settlement cost, verdict. Call before settling on Base when you need a settle-now vs hold recommendation.

• ops.metrics

  Get host OS telemetry: CPU, memory, swap, disk, network, and an ok/warn/critical health verdict. Call to diagnose this MCP host; set include_processes=true for top memory processes.

• city.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 normalized verdict plus source link, not raw portal JSON. Then city.sample, then city.check.

• city.sample

  Free fixed-address preview of paid property-check JSON (verdict, summary, schema). Use before city.check to validate parsing without spending $0.01 USDC.

• city.check

  Is this US address licensed / flagged / showing open violations? One city.check ($0.01 USDC, x402 on Base) returns verdict, summary, dates, and source_url. Unpaid → PaymentRequired; pay via _meta['x402/payment']. Prefer city.sample first.

• 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 compatibility, checks for a2a-x402 and AP2 payment extensions, and extracts callable skills with pricing.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified with the GitHub account kwizzlesurp10-ctrl, which owns the repo

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 182 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 21 tool descriptions and found no hidden instructions to the AI

Compared with others in Law & government datai

• More stars than 0% of the other 1744 servers in this category
• Published to the registry more recently than 60% of the other 1744 servers in this category
• Basic checks equal to or better than 100% of the other 1744 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

No README found in the repo