x402 native · MCP standard

Pay-per-call MCP servers for AI agents.

No accounts. No API keys. No monthly contracts. Just HTTP 402, settled on Base in seconds. Built for autonomous agents that buy data without a human in the loop.

Read the docs View on GitHub

Two servers. Both live. Both autonomous.

Each server speaks the Model Context Protocol and accepts payment via x402 or Apify. Connect from any MCP-compatible agent.

Finance

Toolstem Financial Intelligence

Real-time stock fundamentals, market data, and global equity quotes (US, EU, APAC). Earnings, ratios, peer comps, technicals. Powered by Financial Modeling Prep.

Explore the Finance server

$0.01/call (x402) $0.005/call (Apify)

SEC

Toolstem SEC EDGAR Signal Intelligence

Pay-per-call access to SEC EDGAR filings: 10-K, 10-Q, 8-K, insider transactions, institutional holdings, earnings transcripts. The only x402-listed SEC EDGAR endpoint we know of.

Explore the SEC server

$0.01/call (x402) $0.005/call (Apify)

How it works

An agent calls a tool. The server returns 402 with a payment challenge in the response header. The agent's wallet signs. The server returns data. End to end in seconds.

# 1. Agent attempts the tool call
$ curl -i -X POST https://mcp.toolstem.com/mcp/finance \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
        "params":{"name":"get_quote","arguments":{"symbol":"AAPL"}}}'

# Server responds: HTTP 402 Payment Required.
# The response body is empty {}; the x402 challenge
# is delivered in the `payment-required` HEADER, base64-encoded.

HTTP/2 402
content-type: application/json
payment-required: eyJ4NDAyVmVyc2lvbiI6MiwiYWNjZXB0cyI6W3sic2NoZW1lIjoi...

{}

# Decoded `payment-required` header:
{
  "x402Version": 2,
  "accepts": [{
    "scheme": "exact",
    "network": "eip155:8453",
    "amount": "10000",           // 0.01 USDC, 6 decimals
    "asset": "0x833589fCD...", // USDC on Base
    "payTo": "0xB009DA69...",
    "maxTimeoutSeconds": 60
  }]
}

# 2. Agent's wallet signs EIP-3009 transferWithAuthorization,
#    re-issues the request with the X-PAYMENT header.
#    Coinbase CDP facilitator settles on Base. Server returns data.

$ curl -X POST https://mcp.toolstem.com/mcp/finance \
    -H "X-PAYMENT: <signed-payload>" \
    -d '{"jsonrpc":"2.0","id":1,...}'

# 200 OK — data arrives, payment settled on chain.
{
  "jsonrpc": "2.0", "id": 1,
  "result": {
    "symbol": "AAPL",
    "price": 184.92,
    "change": 1.34,
    "marketCap": 2840000000000
  }
}

Built for the agent stack

No human-only auth flows. No subscription portals. Just a URL and a wallet.

HTTP-native payments

Built on the x402 spec — the same protocol Coinbase, Cloudflare, and CoinGecko use. EIP-3009 USDC on Base mainnet. No bridges, no escrow.

MCP standard

Streamable HTTP transport per the Model Context Protocol spec. Compatible with Claude, Cursor, Cline, LangChain, and any framework that speaks MCP.

Two payment paths

Pay per call via x402 (true agent-to-agent, no humans), or settle monthly via Apify ($0.005/call) if you prefer subscription billing.

Status

Both servers are operational. Live data verified.

Finance

Operational

SEC EDGAR

Operational

x402 facilitator

Coinbase CDP

Settlement

Base mainnet