predmarket-mcp
A monetizable remote MCP server that provides prediction-market intelligence tools for AI agents, enabling discovery, evaluation, and mispricing detection across venues like Polymarket and Kalshi with per-call payment.
README
predmarket-mcp
A monetizable remote MCP server that sells prediction-market intelligence (Polymarket, Kalshi) as tools other AI agents call — and pay for — per call. Not another bot: rails. Normalized data, mispricing detection, and honest realizable edge (after fees/gas/slippage), packaged as tools an agent can lean on instead of building itself.
The server is a thin wrapper over a core/ engine (matcher, signals,
realizable-edge, storage). It returns intelligence only — it never executes
trades or holds funds.
Engine status. Two interchangeable engines share one surface, selected by
CORE_ENGINE(the MCP layer never changes either way):
mock(default) — realistic, same-signature stubs (core/mock.py) so the server works end-to-end offline.live— real Polymarket + Kalshi adapters (core/adapters/) feeding a live engine (core/live.py). Needs network access to the venue APIs; falls back gracefully (empty results) if a venue is unreachable.The shared intelligence (matcher, signals, realizable-edge) lives in
core/algorithms.pyand is used by both engines — not duplicated.
Tool catalog (7 tools, 1 resource, 1 prompt)
Descriptions are the agent's only documentation, so they're written as copy.
Every response carries freshness (as_of / data_age_seconds) and cost
(tier / price_usd).
Free tier (discovery — the funnel)
| Tool | What it answers |
|---|---|
search_markets(query, category?, venue?) |
Discover markets by keyword. |
list_venues() |
Which venues exist, their status and coverage. |
evaluate_market(venue, market_id) |
Prices, implied prob, depth for one market. Data delayed ~60s on the free tier. |
Paid tier (per-call revenue — realtime)
| Tool | What it answers | Price/call |
|---|---|---|
find_mispricing(min_edge, kind?, category?) |
Flagship. Live opportunities above a realizable edge threshold. | $0.05 |
compare_across_venues(event) |
Same event across venues: spread, direction, match confidence. | $0.02 |
estimate_execution(legs, size_usd) |
Realizable edge at your size from current depth, before you act. | $0.01 |
get_market_history(venue, market_id, from_ts, to_ts) |
Historical price/spread series. | $0.01 |
Prices live in pricing.yaml, never hardcoded.
- Resource:
market://{venue}/{market_id}— market snapshot for agents that prefer resources over tool calls. - Prompt:
arbitrage_scan_workflow(min_edge)— guides an agent scan → confirm → estimate execution → rank.
Quick start
uv sync # Python 3.12, deps
uv run pytest # 22 tests, all green
uv run python -m predmarket_mcp.server # streamable-http on http://0.0.0.0:8000/mcp
curl -s http://127.0.0.1:8000/health # {"status":"ok",...}
# live data from Polymarket + Kalshi (needs network egress to the venue APIs):
CORE_ENGINE=live uv run python -m predmarket_mcp.server
Verify with the official MCP Inspector (see tests/test_inspector.md):
npx @modelcontextprotocol/inspector # UI → Streamable HTTP → http://127.0.0.1:8000/mcp
Connecting from a client
Direct HTTP agent (Cursor, LangGraph, any MCP client that speaks Streamable HTTP):
{
"mcpServers": {
"predmarket": { "url": "https://your-host/mcp", "transport": "streamable-http" }
}
}
stdio-only hosts (Claude Desktop / Claude Code) — bridge to the remote server
with mcp-remote:
{
"mcpServers": {
"predmarket": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://your-host/mcp"]
}
}
}
Monetization
Two rails; x402 is primary, API-key/metering is the fallback. Both are inert until you flip the flag — the server can take money, but doesn't gate at launch (usage first, billing later).
PAID_ENABLED=false # default: paid tools run free, metering still records usage
PAID_ENABLED=true # enforce the gate on paid tools
PAYMENT_RAIL=x402 # or "apikey" for the OAuth/metering fallback
x402 (agent-native, stablecoin micropayments)
A paid tool call without a signed X-PAYMENT header gets a real HTTP 402
with an x402 challenge (scheme, network, amount, pay-to). Retry with a valid
base64-JSON X-PAYMENT header → the Facilitator verifies it, a receipt is
logged, and the call is forwarded. Settlement in USDC.
The default
MockFacilitatordoes structural verification and stubs settlement (# TODO: real facilitator/settlement). The 402 flow, gating, and receipt log are real.
Metering (fallback)
Every paid call writes exactly one usage record via a pluggable
MeteringBackend. Default is local SQLite (zero infra); StripeBackend /
MoesifBackend are typed stubs behind the same interface. OAuth 2.1 for the
API-key rail is wired via FastMCP helpers (auth.py), enabled by env.
Configuration (all via env — no secrets in code)
| Var | Default | Purpose |
|---|---|---|
CORE_ENGINE |
mock |
mock (offline stubs) or live (Polymarket/Kalshi adapters). |
PAID_ENABLED |
false |
Master gate switch. |
PAYMENT_RAIL |
x402 |
x402 or apikey. |
FREE_TIER_DELAY_SECONDS |
60 |
Free-tier data delay. |
METERING_BACKEND |
local |
local | stripe | moesif. |
METERING_DB_URL |
sqlite:///metering.db |
Usage/receipt store. |
HISTORY_DB_URL |
sqlite:///history.db |
Price-history store (live mode); Postgres/Timescale DSN for production. |
X402_OPERATOR_WALLET |
— | Payee address for x402. |
X402_NETWORK |
base-sepolia |
Settlement network. |
X402_FACILITATOR_URL |
— | External facilitator (optional). |
AUTH_JWKS_URI / AUTH_ISSUER / AUTH_AUDIENCE |
— | OAuth 2.1 fallback. |
HOST / PORT |
0.0.0.0 / 8000 |
Bind address. |
Deploy
docker build -t predmarket-mcp .
docker run -p 8000:8000 -e PAID_ENABLED=false predmarket-mcp
Runs on Cloud Run / Container Apps / any container host. Streamable HTTP is
serverless-compatible. Terminate TLS and rate-limit at the proxy; use /health
for liveness. The container starts via python -m predmarket_mcp.server so the
x402 ASGI middleware is wired in (equivalent to fastmcp run + payment gating).
Layout
src/predmarket_mcp/
server.py FastMCP app, /health, registration, HTTP app + middleware
tools.py the 7 tools (call core/, format for agents — no logic here)
resources.py market:// resource
prompts.py arbitrage_scan_workflow
config.py env-driven settings (PAID_ENABLED flag)
deps.py the ONLY seam into core/
auth.py OAuth 2.1 fallback wiring
billing/ tiers.py · metering.py · x402.py · middleware.py
core/
models.py canonical pydantic models
algorithms.py shared matcher / signals / realizable-edge (mock + live reuse)
mock.py realistic offline engine (default)
live.py live engine: adapters + algorithms, TTL-cached, history ingest
storage.py price-history store (SQLite default, Timescale/PG via env)
adapters/ base.py · polymarket.py · kalshi.py (fetch + normalize only)
tests/ test_tools.py · test_billing.py · test_adapters.py · test_storage.py · test_inspector.md
Design principles honored
- ≤ 15 tools (7 here) — agent tool-selection degrades past ~25–30.
- Tools are shaped around agent questions, not 1:1 API endpoints.
- Realizable edge, never gross. Every response marks data staleness.
- No custody, no auto-execution — intelligence only.
core/logic is not duplicated — tools call the engine.- Secrets via env only.
Note on FastMCP version
The spec referenced "FastMCP 3.x"; this builds on the current
fastmcp 3.x (decorator API, Streamable
HTTP, OAuth helpers). SSE is intentionally unused (deprecated).
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.