Back to Browse

X402 Examples MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Pay-per-call agent tools via x402 (USDC on Base): chat, prices, funding, RNG. No account or keys.

About

Pay-per-call agent tools via x402 (USDC on Base): chat, prices, funding, RNG. No account or keys.

Remote endpoints: streamable-http: https://x402.shizu.me/mcp/rpc

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

5 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-scrape402-scrape402": {
      "url": "https://x402.shizu.me/mcp/rpc"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

x402 examples — pay-per-call APIs for AI agents

Working examples for calling x402-gated HTTP APIs: your agent pays USDC per request on Base — no signup, no API keys, no subscription.

All examples run against x402.shizu.me (77 live endpoints, prices from $0.001/call): an OpenAI-compatible LLM gateway (/v1/chat/completions, /v1/embeddings, /v1/models), web search, a code sandbox, web scraping, live crypto/market data, verifiable randomness, and a prepaid off-chain metering rail for high-frequency loops (100+ calls/min, no per-call gas).

How x402 works

  1. Call any endpoint → the HTTP 402 response carries signed USDC payment requirements (price, asset, recipient).
  2. Pay — your x402 client signs the payment locally and retries automatically.
  3. Served — settlement is on-chain; you are only charged when the call succeeds. Errors and 4xx never settle.

Fund a wallet with a few dollars of USDC on Base, export its private key, and every example here just works.

JavaScript

npm install x402-fetch viem
export X402_PRIVATE_KEY=0x...   # wallet holding USDC on Base
node js/chat.mjs

Python

pip install x402 eth-account httpx
export X402_PRIVATE_KEY=0x...
python python/chat.py

Examples

FileWhat it shows
js/chat.mjsOpenAI-compatible chat completion, paid per call
js/search.mjsLive web search without a search-API account
python/chat.pyChat completion via the Python x402 client
python/embeddings.pyOpenAI-shape embeddings for RAG loops
python/metered_loop.pyPrepay once, then 100+ calls/min off-chain

Just looking?

Every route quotes its price on a free unpaid request:

curl -i https://x402.shizu.me/crypto        # → 402 + payment requirements
curl https://x402.shizu.me/llms.txt          # full catalog, agent-readable

Links

Live service: https://x402.shizu.me · OpenAPI: https://x402.shizu.me/openapi.json · MCP tools: https://x402.shizu.me/.well-known/mcp-tools · Contact: x402@opklaar.com

MIT licensed.

Reviews

No reviews yet

Be the first to review this server!