Curade — prediction-market & perp-funding data (x402)
RemoteAbout Curade — prediction-market & perp-funding data (x402)
Curade is a remote MCP server for paid prediction-market and perpetual-funding data from its API. Its four tools return Polymarket odds and market comparisons, attested market packages, and Hyperliquid funding rates; calls are paid individually through x402 in USDC on Base.
Key features
- 01Retrieve Polymarket odds snapshots
- 02Compare Polymarket and Kalshi markets
- 03Get signed market data packages
- 04Fetch Hyperliquid funding rates and APR
Use cases
- 01Inspect current prediction-market odds
- 02Find disagreement between two venues
- 03Obtain an attested package for a market
- 04Review coin funding rates and APR
MCP support
Exposes four paid data tools over streamable HTTP at `https://curade.xyz/mcp`. Each data call uses x402 payment in USDC on Base; initialization and tool listing are free.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://curade.xyz/mcpclaude mcp add --transport http sryantrabot-curade https://curade.xyz/mcp{"mcpServers":{"sryantrabot-curade":{"type":"http","url":"https://curade.xyz/mcp"}}}Open in Cursor{"servers":{"sryantrabot-curade":{"type":"http","url":"https://curade.xyz/mcp"}}}Open in VS Code{"mcpServers":{"sryantrabot-curade":{"type":"http","url":"https://curade.xyz/mcp"}}}{"mcpServers":{"sryantrabot-curade":{"serverUrl":"https://curade.xyz/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEcurade-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:
| Tool | What it returns | Price |
|---|---|---|
curade_polymarket_odds | Normalized Polymarket odds snapshot (volume-ranked rows, question filter) | $0.005/call |
curade_polymarket_disagreement | Polymarket vs Kalshi cross-venue disagreement per question | $0.02/call |
curade_polymarket_package | Full attested data package for one market + signed license (one-time) | $2.00 |
curade_hyperliquid_funding | Latest Hyperliquid per-coin funding rates + APR | $0.001/call |
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-Signatureheader. - 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
# 1. initialize + tools/list (free, no payment)
curl -s -X POST https://curade.xyz/mcp -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
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).
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.