# Prediction Market Tools with an MCP Server Cards that publish a Model Context Protocol server — what an agent can call, which of those tools write, and where your key sits while it does. *https://predictionmarkets.tools/collections/mcp-servers* ## What the flag on these cards means `interfaces.mcp_server` says one thing: the vendor publishes a Model Context Protocol server for this product. An MCP server is a process, or an endpoint, that describes the product to an agent client as a list of named tools with typed arguments — so a model can call `get_market` or `place_paper_order` the way it would call a function, without you writing a client first. That is a packaging fact, not a quality one. It says the data you could already have fetched over REST is now reachable by something that decides for itself which call to make next, and — on a minority of these cards — that some of those calls change state. Nothing else about the product follows from it. The distinction worth holding on to is that the agent is not reading a page. It is being handed a capability list by the vendor, and it will use what is on that list. What is on the list is therefore the whole of the security question, and it is printed by the server itself. ## Read, prepare, write — three things behind one word **Most of this listing is read-only.** [Adjacent](https://predictionmarkets.tools/tools/adjacent) exposes four tools — `list`, `find`, `get` and `price`. [Dune](https://predictionmarkets.tools/tools/dune-polymarket-dashboards) exposes table discovery, search by contract address, saved queries, query execution, results and credit usage. [Orcalayer](https://predictionmarkets.tools/tools/orcalayer) pipes whale trades and wallet metrics into a client. [Depthfeed](https://predictionmarkets.tools/tools/depthfeed) returned fifteen tools to an unauthenticated `tools/list` call on 19 September 2026 — search, order books, snapshots and candles across three venues, plus `bars`, `backtest_paths`, a `screener` and `whoami`. An agent given any of these can be wrong about your research; it cannot be wrong about your balance. **Two cards sit in the middle, and this is the shape to prefer.** [Polyrama](https://predictionmarkets.tools/tools/polyrama) exposes ten tools and exactly one of them writes: `place_paper_order`. Its API's `write:live` scope is documented as reserved for future live trading, so the answer to "can the agent trade" is no, in a way you can check rather than trust. [Limitless](https://predictionmarkets.tools/tools/limitless-api) does the other version of the same idea — its first-party server searches markets, reads books and price history, and *prepares* orders that a human then approves in the browser. It is non-custodial and holds no keys at all. **A few go all the way to the exchange, and they all make you ask twice.** [CCXT](https://predictionmarkets.tools/tools/ccxt) ships `ccxt-mcp`, run locally over stdio, which exposes market data, balances and opt-in trading; trading, withdrawals and raw endpoints are separate opt-in tiers and are off by default. [Predictefy](https://predictionmarkets.tools/tools/predictefy) publishes the most explicit inventory in the catalogue: 42 tools by default, of which 33 are read, intelligence and platform tools and 9 are paper-trading tools, with a further 10 execution and collateral tools that do not appear at all unless `MCP_ENABLE_TRADE` is set. No single tool both builds and submits an order, new keys are read-only until a `trade` scope is added, and spend caps default to 100 US dollars per order and 1,000 per key per rolling 24 hours. [Myriad](https://predictionmarkets.tools/tools/myriad) runs its server from a first-party CLI for agent-driven trading, and [PMXT](https://predictionmarkets.tools/tools/pmxt) hands `@pmxt/mcp` the venue-native credentials — a Polygon private key for Polymarket, an API key plus an RSA private key for Kalshi. On the on-chain venues that last point is the whole of it: the key that signs an order is the key that moves the collateral. There is no read-only version of it to hand over. ## Where the key lives Three arrangements, and they fail differently. - **Local process, key in the environment.** `npx predexon-mcp` with the key in an environment variable ([Predexon](https://predictionmarkets.tools/tools/predexon)), `npx -y @predictefy/mcp`, CCXT over stdio with the keys never leaving the machine. The exposure is your machine and whatever else runs on it. - **Hosted endpoint, key over the wire.** [FinFeedAPI](https://predictionmarkets.tools/tools/finfeedapi) takes it in an `X-APIKey` header; Adjacent takes it as an `apiKey` query parameter for the realtime tier — and a credential in a query string is a credential in somebody's access log. [Polymarket Analytics](https://predictionmarkets.tools/tools/polymarket-analytics) is the same shape with a bearer token, and [Apify](https://predictionmarkets.tools/tools/apify-prediction-market-scrapers)'s host at least fails honestly, answering an unauthenticated request with a 401 rather than a 404. - **Your account, not a key at all.** Dune's server authenticates over OAuth against your Dune account and draws on the same credit allowance as everything else you run there. There is no narrower thing to hand it, and an agent that loops costs you credits rather than a rate-limit error. ## What to ask before you connect one 1. **What does it export?** Call `tools/list` and read it. It takes a minute, several of these answer it with no key, and it is the only description of the server that cannot be out of date. 2. **Which of those tools write, and what does a write mean here?** A simulated fill, an order parked for a human to approve, or a signed order against real collateral are three different answers, and the tool name usually says which — `place_paper_order` is not ambiguous. 3. **Where does the credential sit, and how narrow can it be made?** Environment variable in a local process, header to a vendor's host, or an OAuth session over a whole account. Ask whether a read-only key exists, whether trading is a separate scope, and whether there is a spend cap. Predictefy answers all three in its own documentation; most do not. ## What the flag does not tell you It is not a claim about the data. It is not a claim about the licence: Polyrama's MCP server is MIT-licensed and published as `@polyrama/mcp`, while the terminal and the API behind it are not open source, and the server needs a Polyrama token to be useful at all. It is not a claim about stability — Predictefy's SDK, CLI and MCP packages are all on beta lines and its own documentation says to pin an exact version rather than track `latest`, and PMXT's last release was 18 July 2026. And it is not a claim that the product is free: Artemis carries REST, MCP and a Snowflake share together on the tier its documentation prices from 50,000 US dollars a year. It is also the fastest-moving field on any of these cards. A server that exposed four read tools in September can expose a write one in November without the product changing its name, which is the reason step 1 above is "ask the server" and not "read this page". Nothing in this collection has been connected to a funded account by this site. The tool inventories, the scopes and the defaults above are read from vendor documentation and from unauthenticated protocol calls, both dated on the cards. ## Cards - [Adjacent](https://predictionmarkets.tools/tools/adjacent.md) — Prediction-market indices and reference rates, with Kalshi on the tier you can test. - [Airavat](https://predictionmarkets.tools/tools/airavat.md) — Trader scoring, filters and paper-trading pods over Polymarket. Invite-only. - [Apify prediction-market scrapers](https://predictionmarkets.tools/tools/apify-prediction-market-scrapers.md) — A store of third-party actors that normalize Kalshi and Polymarket into one row shape. - [Artemis prediction-market metrics](https://predictionmarkets.tools/tools/artemis-prediction-markets.md) — Daily volume, open interest and fees across thirteen event venues, with methodology. - [CCXT](https://predictionmarkets.tools/tools/ccxt.md) — One client for seven prediction venues, inside a 104-exchange crypto library. - [DepthFeed](https://predictionmarkets.tools/tools/depthfeed.md) — The recorded bid-ask ladder for crypto up-or-down markets, which no venue keeps itself. - [Polymarket dashboards on Dune](https://predictionmarkets.tools/tools/dune-polymarket-dashboards.md) — Community SQL dashboards over Polymarket's on-chain record, free to read and fork. - [FinFeedAPI Prediction Markets API](https://predictionmarkets.tools/tools/finfeedapi.md) — Nine event venues normalized into one REST schema, billed by usage credit. - [Limitless API](https://predictionmarkets.tools/tools/limitless-api.md) — REST and WebSocket for markets, books, candles and trading on Base. - [Limitless](https://predictionmarkets.tools/tools/limitless.md) — Event contracts on Base, collateralised in USDC, traded on a central limit order book. - [Myriad](https://predictionmarkets.tools/tools/myriad.md) — Multi-chain event markets priced by an AMM and settled in stablecoins or in points. - [OrcaLayer](https://predictionmarkets.tools/tools/orcalayer.md) — Polymarket whale analytics indexed from Polygon, with a published farmer filter. - [PMXT](https://predictionmarkets.tools/tools/pmxt.md) — CCXT-shaped client for prediction markets, with a hosted API and a self-hosted mode. - [Polymarket Analytics](https://predictionmarkets.tools/tools/polymarket-analytics.md) — Third-party Polymarket wallet, trader and market analytics, free to browse. - [PolyOrderbooks](https://predictionmarkets.tools/tools/polyorderbooks.md) — Recorded L2 books for Polymarket crypto markets, priced by how far back you may look. - [Polyrama](https://predictionmarkets.tools/tools/polyrama.md) — Polymarket and Kalshi in one terminal, with wallet analytics and a REST API. - [Predexon](https://predictionmarkets.tools/tools/predexon.md) — Tick-level book history as Parquet, billed by the gigabyte, plus a mempool-aware feed. - [Predictefy](https://predictionmarkets.tools/tools/predictefy.md) — Sixteen venues behind one verb family, priced in credits, with nothing readable for free. ## FAQ ### Does an MCP server mean an agent can trade for me? Usually not, and never by default on any card here. Most of these servers are read-only. Where a write path exists it is fenced - Polyrama exposes ten tools of which the only write is place_paper_order, Limitless prepares an order that a human approves in the browser, and both CCXT and Predictefy ship execution switched off until you set it. Read the tool list before you assume either way. ### How do I find out what a server actually exposes before connecting it? Ask it. The MCP protocol has a tools/list call, and several of these answer it without credentials - Depthfeed returned fifteen tools to an unauthenticated tools/list on 19 September 2026, and Adjacent's server answers its four tools at a 15-minute delay with no key. Where a key is required the host should answer 401 rather than 404, which is what Apify's does. ### Does the vendor publishing an MCP server mean I can use it? Not on its own. It can sit behind the top plan - Artemis puts the REST API, the MCP server and the Snowflake share together on the tier its documentation prices from 50,000 US dollars a year - and it can be a beta package the vendor tells you to pin to an exact version, which is what Predictefy says about its own. ### Where does my API key live when I connect one of these? In one of three places, and the difference matters. A local server runs on your machine and reads the key from the environment - predexon-mcp and the Predictefy server both run through npx, and CCXT's runs over stdio with the keys never leaving the machine. A hosted server takes the key over the wire, in a header or a query parameter. Dune's takes neither - it authenticates your whole Dune account over OAuth and spends the same credit allowance everything else does.