
Connects to Manifold Markets, the play-money prediction market platform where you can bet on anything from election outcomes to personal goals. The source doesn't list specific tools, but it's part of the Pipeworx gateway ecosystem, which offers an ask_pipeworx interface that lets you query in plain English instead of calling APIs directly. Useful if you're building agents that need to read or interact with prediction market data, check odds on events, or integrate forecasting into workflows. Available as a standalone server or through the full Pipeworx gateway that bundles 865+ data sources.
Manifold Markets MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
search_markets | Search Manifold Markets prediction markets by topic or question text. Returns markets with current probability (for binary), trading volume, liquidity, bettor count, and resolution status. Manifold is a play-money venue with tens of thousands of user-created markets on any topic. Keyless. |
get_market | Get full detail for a single Manifold market by its URL slug or id. Provide exactly one of slug/id. For multiple-choice markets, returns each answer with its probability (top 12). Includes plain-text description, creator, volume, liquidity, and resolution. Keyless. |
top_markets | Most-active open Manifold markets right now — a live attention/demand signal for what the prediction-market crowd is trading. Optionally narrow to a topic. Returns compact market records sorted by popularity. Keyless. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"manifold": {
"url": "https://gateway.pipeworx.io/manifold/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/manifold/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Manifold data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
curl -X POST https://gateway.pipeworx.io/v1/tools/manifold_search_markets \
-H 'Content-Type: application/json' \
-d '{"term":"2026 election"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/manifold_search_markets. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.