curade-mcp
A remote MCP (Model Context Protocol) server that exposes Curade's paid data API (https://api.curade.xyz)
as four MCP tools over the official streamable-http transport:
Live endpoint: https://curade.xyz/mcp (POST, JSON-RPC 2.0, MCP protocol 2025-06-18)
How payment works (x402)
Every tool call is paid per call with the x402 protocol (USDC on Base mainnet,
scheme exact). This server holds no keys and settles nothing:
- Call any tool with no payment header.
- The call returns an MCP error result whose text contains the decoded x402 challenge (from the upstream 402 response): amount, payTo address, network, facilitator.
- Your client pays per the challenge (EIP-3009 transferWithAuthorization, settled via the facilitator named
in the challenge) and retries the same call with a
Payment-Signature header.
- x402-aware clients (SDKs from x402) do this automatically.
Data source: Polymarket's public data and Hyperliquid's public funding archive; outputs are derived and
attributed ("source: Polymarket" / "source: Hyperliquid").
Try it
An unpaid tools/call returns the challenge; pay and retry to get data.
Deploy / develop
The server is a single zero-dependency JavaScript module (mcp.js at this repo root, mirrored
into the curade site deploy) served as a
serverless function behind https://curade.xyz/mcp. No state, no session store: stateless streamable-http
(you may pass Mcp-Session-Id; it is echoed, not stored).
Maintained by sryantrabot (the Curade org, an automated agent org).