← Registry

API Tools

x402-mcp.onrender.com

Facilitates payment-based access to HTTP services using the x402 protocol.

x402 supported1 endpoint19 known toolsFirst detected July 25, 2026Last detected September 24, 2026

ENDPOINT 1

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

No auth detected

MCP server metadata

Name
x402-micropayments
Version
1.30.0
Capabilities
experimentalpromptsresourcestools
Server instructions

x402 micropayments MCP (USDC on Base). Route by domain: x402.* buyer/seller HTTP 402, commerce.* quota/credits/Stripe, swarm.* composite research resale, pulse.base settlement timing, ops.metrics host health, city.* US open-data property compliance. Buyer path: x402.discover → x402.probe → x402.pay_and_fetch. City path: city.list → city.sample → city.check. Pro quota: commerce.pro_requirements → pay → commerce.activate_pro. Credits: commerce.credits_requirements → pay → commerce.purchase_credits. Public seller hosts have no spend key — probe tools still work; pay-and-fetch needs EVM_PRIVATE_KEY. Every tool response includes commerce meta.

Known tools 19

x402.agent_card

Return the A2A Protocol v1.0 Agent ID Card and MCP server card.

Inferred read-only
x402.discover

Discover paid HTTP APIs in the x402 Bazaar via the facilitator catalog.

Inferred read-only
x402.probe

Probe a URL for HTTP 402 PAYMENT-REQUIRED terms using the x402 client SDK.

Potential side effects
x402.pay_and_fetch

Pay USDC via x402 and fetch a protected HTTP resource in one call.

Potential side effects
x402.build_seller

Build seller-side x402 payment requirements for your own HTTP resource.

Potential side effects
x402.verify

Verify an x402 PAYMENT-SIGNATURE against PAYMENT-REQUIRED terms via the facilitator.

Potential side effects
x402.networks

List supported settlement networks, facilitators, and x402 v2 header names.

Inferred read-only
commerce.pro_requirements

Build x402 payment requirements to purchase the Pro quota tier.

Potential side effects
commerce.activate_pro

Verify a Pro-tier x402 payment and unlock Pro quota limits for the agent.

Potential side effects
commerce.credits_requirements

Build x402 payment requirements to buy a pack of per-use MCP tool credits.

Potential side effects
commerce.purchase_credits

Verify an x402 payment and add per-use tool credits to the agent.

Potential side effects
swarm.research

Run the swarm agency: compose a research product from free inputs and list it for resale.

Inferred read-only
swarm.settle

Verify and settle a buyer's x402 payment for a listed composite product and record revenue.

Potential side effects
swarm.revenue

Get swarm composite economics: spend, composite sales, LTV:CAC, margins, per-source scores.

Inferred read-only
pulse.base

Get live Base Network Pulse: base fee, EIP-1559 projection, utilization, USD settlement cost, verdict.

Inferred read-only
ops.metrics

Get host OS telemetry: CPU, memory, swap, disk, network, and an ok/warn/critical health verdict.

Inferred read-only
city.list

List US City Open-Data Compliance Network cities with paid_url, sample_url, and price.

Inferred read-only
city.sample

Get a free fixed-address property compliance sample for one US city code.

Inferred read-only
city.check

Run a paid US city property compliance check via x402 on the same HTTP resource buyers use.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.x402-micropayments]
url = "https://x402-mcp.onrender.com/mcp/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "x402-micropayments": {
      "type": "http",
      "url": "https://x402-mcp.onrender.com/mcp/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: x402-micropayments
Remote MCP URL: https://x402-mcp.onrender.com/mcp/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "x402-micropayments": {
      "url": "https://x402-mcp.onrender.com/mcp/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "x402-micropayments": {
      "type": "http",
      "url": "https://x402-mcp.onrender.com/mcp/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "x402-micropayments",
  "transport": "streamable-http",
  "url": "https://x402-mcp.onrender.com/mcp/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for onrender.com was fetched 2026-09-27T04:50:32.253Z.

Trust status Trusted

onrender.com is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.