Paddock

What the Paddock MCP server does

The Paddock MCP server helps agents evaluate x402 services and inspect activity in the agent-payment market. Its pre-payment check probes a target endpoint, compares the observed payment contract with expected terms and the provider's published configuration, and adds evidence about settlement recency, circular activity, and price relative to the market. The result includes a route verdict of true, false, or inconclusive with dated evidence.

It also provides market snapshots covering transaction volume, USDC spend, buyers, providers, category share, reliability, and changes over time. Data covers activity on Base and Solana. The HTTP API can be called directly by agents, with per-query payment supported through x402.

Tools and capabilities

The twelve MCP tools cover these use cases:

• get_market_summary returns current market totals and leading categories without authentication.
• verify_before_pay checks a target before payment.
• get_category_detail lists services, pricing, transaction counts, provider counts, and reliability for supported categories.
• get_niche_gaps ranks categories by demand and provider opportunity.
• get_best_value_provider ranks providers using reliability, unique buyers, and price.
• get_liveness reports domain status, probe success, latency, endpoint count, and recent probe timing.
• get_changes compares a current snapshot with a date up to 90 days earlier.
• get_circular_signal and get_whale_activity provide aggregate settlement analysis without wallet addresses or operator identities.
• get_token_metrics returns chart and time-series data, including spend share, transactions, liveness, concentration, new services, and the Agent Commerce Index.
• get_provider_revenue reports attributed provider revenue while identifying incomplete or unattributed data.
• get_report_data supplies free report metadata and paid structured report data.

Paddock can also produce signed attestations for pre-payment checks. These JSON records contain observed terms, settlement evidence, an observation window, and a verdict. Ed25519 signatures use RFC 8785 canonicalization, and records can be checked independently with the published public key.

How it works

The remote MCP endpoint is https://paddock.finance/api/mcp/mcp. It uses standard MCP HTTP transport, so a compatible client can connect to the URL and discover the available tools. The repository's openapi.json mirrors the live specification and can be used for route and schema discovery, although the live specification is authoritative if the files differ.

get_market_summary is unauthenticated. Five other tools use a free key with ten calls per UTC day shared across those tools. Paid tools accept a Paddock API key, a per-query x402 payment, or, where available, one free trial call per day per IP. The paid report route has no full-data trial, while report metadata remains free.

Setup and configuration

The Paddock MCP server does not require a local installation in the documented setup. In Claude Desktop, add a custom connector and provide the MCP URL. Other MCP clients can use the same endpoint as a standard HTTP server. For paid calls using a subscription, pass the Paddock API key as the api_key tool argument; the connector forwards it as X-Paddock-Key. Omitting that argument selects the applicable free trial or x402 payment path.

For independent attestation checks, fetch the public key from /.well-known/paddock-attestation-key, retrieve the record, canonicalize it according to RFC 8785, and verify its Ed25519 signature.

Limitations and notes

Liveness results apply to domains TrustBench probes and use a nightly rollup. Revenue analysis excludes facilitator pass-through and circular-flagged wallets; unresolved wallets appear as an unattributed row without a dollar amount. Circular and whale results are aggregated and do not identify wallets or operators. Paid-tool prices and access rules vary by tool, so clients should inspect the live specification before selecting a billing method.