mcp server
Mantis
Cross-venue prediction market routing for AI agents with arbitrage, quotes, history, and signals.
Description as published by the maintainer. Source
- version 1.1.4
- archived
- retrieval
archived — The linked repository returns 404. It was deleted, renamed or made private. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
6 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
execute_url(side, amount, source, market_id, route_query, canonical_id)- Get a deep link URL to place a trade on the best venue for a given market. The URL has a referral code embedded so the platform earns commission. Call this to get the URL, then direct the user to open it.
get_arbitrage(venue_a, venue_b, include_fees, position_size, min_spread_pct)- Find live cross-venue arbitrage opportunities — markets where the same event trades at different prices on Polymarket vs Kalshi vs other venues. Can also estimate fee-normalized net spread for a position size.
get_history(to, from, venue, format, market_id, granularity, canonical_id)- Get historical OHLCV-style prediction market candles over a time range, including the latest stored depth snapshot within each bucket when available. Can also export CSV text or base64-encoded Parquet. Required: from, to.
get_quote(size, market_id, canonical_id)- Get the live probability, liquidity, and volume for a prediction market across all venues. Can also return venue order book depth and size-aware VWAP/slippage estimates.
get_unmet_demand(days, limit)- Find questions that users are searching for but no prediction market exists. Useful for discovering new market creation opportunities or identifying emerging topics with real trading interest.
route_market(q)- Find the best prediction market for a natural-language question or trading intent. Returns the best cross-venue match, current probability, liquidity, and any arbitrage opportunity between venues. Required: q.
Last successful function declaration observed on . Source: https://mantiss.store/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mantiss.store/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.1.4 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-14 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-14 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | not_found | GitHub returned 404 for the repository the maintainer listed. The project was deleted, renamed or made private, so the listing points at nothing. | as of fetch | GitHub | |
| mcp tools declared | 6 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mantiss.store | |
| mcp endpoint status | ok | The server listed 6 functions when asked. | as of probe | mantiss.store |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json