Mercury402: Treasury/FRED financial data over x402
Server Details
Treasury/FRED financial data over x402: pay-per-call US yields, macro and forex in USDC on Base
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- dudman1/mercury402
- GitHub Stars
- 1
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
list_endpoints and get_endpoint_data have clearly different roles: discovering endpoints versus invoking one. The descriptions make the boundary clear, though the hosted get_endpoint_data only returns 402 payment instructions, which could still surprise an agent expecting data.
Both names follow a verb_noun snake_case pattern (list_endpoints, get_endpoint_data). The noun forms are slightly inconsistent (endpoints vs endpoint_data), but the convention is still predictable.
Two tools is thin for a server fronting 78 financial endpoints, though the generic list-and-call design is intentionally minimal. It sits at the borderline of being too sparse, especially without filtering or search helpers.
The set covers endpoint discovery and invocation, but the hosted invocation tool does not return actual financial data—only HTTP 402 payment instructions. There is no integrated payment or wallet flow, so agents cannot complete the core data-retrieval task without an external x402 client.
Available Tools
2 toolsget_endpoint_dataCall a Mercury402 endpointAInspect
Call a Mercury402 endpoint on the live API. This hosted endpoint is discovery-only: endpoints return HTTP 402 and this tool returns the price and x402 payment instructions instead of data. Pay with your own x402 client, or run mercury402-mcp locally (npx -y mercury402-mcp) with your own wallet. Use list_endpoints first to find paths and parameters. Path params can be inline ("/v1/fred/UNRATE") or passed in params ("/v1/fred/{series_id}" + {"series_id":"UNRATE"}). Other params go to the query string (GET) or JSON body (POST).
Inputs: path (required), pay, params.
list_endpointsList Mercury402 endpointsARead-onlyInspect
List Mercury402 financial data endpoints (78 total) with path, method, category, description, price in USD (paid per call in USDC on Base via x402) and accepted parameters. Free; makes no network calls.
Inputs: search, category.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Pay-per-call tools for agents: onchain data, ECB FX rates, text tools. USDC on Base, x402
Market and on-chain crypto data for AI agents. Pay per call in USDC on Base (x402).
Live financial data MCP: FX, crypto, stocks, news, URL reader. x402 on Base: $0.001/call.
34 pay-per-call AI and data tools over x402; USDC on Base; no API keys.
Related MCP Servers
- AlicenseAqualityDmaintenancePay-per-call x402 data products on Base mainnet — sanctions screening, aviation weather, mortgage rates, US property dossier, title chain, wallet balance, and agent session auth. Every call settles in USDC with an on-chain receipt, no accounts or API keys.7115 npmMIT

hyperd-mcpofficial
AlicenseAqualityDmaintenancePre-trade DeFi intelligence for AI agents. 20 paid x402 endpoints, USDC on Base.2369 npm1MIT- FlicenseNot gradedqualityDmaintenance56 pay-per-call MCP endpoints for AI agents. Market signals, macro economics, crypto/DeFi, geopolitical intelligence, SEC filings, GitHub velocity, sanctions screening. USDC on Base Mainnet via x402.-
- AlicenseNot gradedqualityBmaintenanceProvides real-time stock quotes and batch market data to AI agents, secured via x402 micropayments on Base Mainnet.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.