List your agent

x402 Micropayments MCP

MCP server● Hosted · onlinev1.30.0

Pay-per-call US city property compliance and Base tx checks, paid in USDC on Base via x402

Reviews

No review yet. Used x402 Micropayments MCP? Be the first to help others choose.

What it does

x402 Micropayments MCP is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.30.0
PriceNot in the registry
First seen26 Sept 2026
Last checked5d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 21h ago (live check)

Hosted endpoint

  • https://x402-mcp.onrender.com/mcp/mcp streamable-http

In Claude Code: claude mcp add --transport http x402-mcp-1 https://x402-mcp.onrender.com/mcp/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

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

Live check

Electra Index connected to the hosted endpoint 21h ago

ONLINE x402 Micropayments MCP answered an MCP connection on 13 Nov 2026 and introduced itself as x402-micropayments 1.30.0 (MCP protocol 2025-06-18).

21 tools offered to AI assistants

  • 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. Unpa
  • 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-SIGNA
  • 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_requirement
Show 9 more
  • 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
  • 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.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://x402-mcp.onrender.com/mcp/mcpDECLAREDSRC-001 Official MCP Registry5d ago
Version1.30.0DECLAREDSRC-001 Official MCP Registry5d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry5d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry5d ago
Websitehttps://x402-mcp.onrender.comDECLAREDSRC-001 Official MCP Registry5d ago
Repositoryhttps://github.com/kwizzlesurp10-ctrl/x402-mcpDECLAREDSRC-001 Official MCP Registry5d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry5d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry5d ago

Change history

  • VERSION17 Oct 2026
    0.1.0 → 1.30.0

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run x402 Micropayments MCP? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor x402 Micropayments MCPLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of x402 Micropayments MCP?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/x402-mcp-1?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/x402-mcp-1/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about x402 Micropayments MCP

How do I connect x402 Micropayments MCP?

Use the hosted endpoint https://x402-mcp.onrender.com/mcp/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does x402 Micropayments MCP offer?

When Electra Index connected on 13 Nov 2026, it listed 21 tools: x402.agent_card, x402.discover, x402.probe, x402.pay_and_fetch, x402.build_seller, x402.verify, x402.policy_check, x402.networks and more. The full list is in "Live check" above.

Is x402 Micropayments MCP online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 21h ago.