actually-mcp-server
This server gives an agent read-only access to live prediction-market odds from Polymarket, so it can anchor news text to what bettors actually think.
check_news— pass in a piece of news text (up to 8,000 chars) and get back the best-matching Polymarket market plus its current YES probability, drawn from a precomputed cache (up to ~2 hours stale, flagged withcacheStale/cacheAgeHoursif abandoned).get_market— look up a specific market bymarketIdfor details, a live price, and an orderbook snapshot for one outcome token (YesorNo), falling back to a direct Gamma lookup for markets outside the cache.Interpretation is left to the agent — the server returns the market's real price, not a judgment on whether the news is true or dramatized.
No key or wallet needed — both tools are read-only and open-world; trading tools (
place_order,sell_order, etc.) only appear if you supply your own private key, and are not part of this schema.
Allows connecting a WalletConnect v2 wallet to place limit and market orders, sell, cancel orders, and view positions on prediction markets.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@actually-mcp-server Check this article against Polymarket markets and show the odds."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Actually - What Markets Really Think
A Chrome extension and an MCP server that put prediction-market odds on top of the news you are already reading.
News tells you that "experts are concerned" or that "odds are rising". It rarely tells you a number. The number exists - on a prediction market, where people are betting their own money on the outcome. It just lives in another tab, and finding it means knowing such a market exists in the first place.
Actually closes that gap. Open an article, click the toolbar icon, and the extension matches the text against live Polymarket markets and shows the market's own probability. No account, no wallet, no signup.
Add it to Chrome from the Chrome Web Store - free.

What it does
Matches an article to a market. A local embedding model (
Xenova/all-MiniLM-L12-v2, ~33 MB) scores the article text against the cached market set, boosted by keyword and number overlap - numbers matter because the encoder is nearly blind to them, and "dip to $57,500" embeds almost identically to "reach $120,000".Runs on your device. Model and WASM runtime are bundled at build time - nothing is fetched from a CDN at install or runtime, and on the default settings the article text never leaves the machine.
Reads non-English pages. They are translated to English before matching, using Chrome's own built-in
TranslatorAPI (local, no network). Every Polymarket question is written in English, and the local model holds 86 Cyrillic tokens out of 30522 - an untranslated Russian headline embeds to noise. Translated, the same headline scores 0.53-0.71 against the market it is actually about, against a 0.35 floor.
Trades, optionally. Connect any WalletConnect v2 wallet for limit and market orders, selling, cancelling resting orders, and a positions panel with cost basis and P&L. Keys and funds are never held by us.
Serves agents too. The same capabilities are exposed over the Model Context Protocol:
check_news,get_market,place_order,sell_order,cancel_order,get_positions.
Related MCP server: Polymarket Predictions MCP
Using the MCP server
The MCP server is published, so it needs no clone and no build. Add it to any MCP client (Claude Desktop, Cursor, and anything else that speaks the protocol):
{
"mcpServers": {
"actually": {
"command": "npx",
"args": ["actually-mcp-server"]
}
}
}That gives an agent the signal tools - check_news and get_market - with no
key and no wallet. Ask it "what do markets think about this?" with a headline
and it answers with the market's own price.
The very first launch downloads the package and its local model runtime (about
170 MB), and the first check_news then fetches the 34 MB model. On a slow
connection that can take longer than a client waits for a server to start; if
yours reports a timeout, run npx -y actually-mcp-server once in a terminal,
let it finish, and restart the client. Later launches start in a few seconds.
Trading tools appear only if you supply a key of your own:
"env": {
"POLYMARKET_PRIVATE_KEY": "0x...",
"ACTUALLY_MAX_ORDER_USD": "100",
"ACTUALLY_DAILY_LIMIT_USD": "500"
}Both caps are enforced server-side against a persisted spend ledger, so an
agent cannot talk its way past them by claiming a different price.
redeem_position needs a further explicit opt-in
(ACTUALLY_ENABLE_REDEEM=true) because it submits a real on-chain transaction
and is still in testing.
Full documentation, including every environment variable and the reasoning
behind the guards: packages/mcp-server/README.md.
Listed in the official MCP registry
as io.github.Sofiia7/actually, on mcpservers.org, and on Glama:
How it fits together
extension/ Chrome MV3 extension (React popup, offscreen document)
extension/worker/ Cloudflare Worker - API proxy, rate limiting, market cache
packages/core/ Matching, pricing and Polymarket API logic, shared by both clients
packages/mcp-server/ MCP server, published to npm as actually-mcp-server
packages/market-cache-builder/ Cron job that precomputes the market embeddingsThe heavy work lives in an offscreen document because MV3 service workers cannot run WASM, hold a WebSocket, or survive long enough to sign an order.
The market cache is 2000 open markets with precomputed embeddings, rebuilt every two hours. Selection blends three orderings - 24h volume, lifetime volume, and recency - because ranking by lifetime volume alone is the wrong shelf for a news tool: a market opened this morning under today's headline has no history and loses to a year-old election market every time.
The Worker exists so no client has to hold a credential. It proxies Polymarket's APIs, serves the precomputed cache, and acts as a remote signer for the relayer, so the builder credential stays on the server and never ships inside an extension.
Running it
npm install
npm run models:fetch -w extension # bundle the embedding model
npm run build -w extension # type-check + build to extension/distLoad extension/dist as an unpacked extension in Chrome. Copy
extension/.env.example to .env.local and fill it in first - the build bakes
the Worker URL, the WalletConnect project id and the builder code.
npm test --workspaces # 822 tests across four workspacesPrivacy
Discovery is free and needs no account. There are no content scripts: the page is read only when you click, and only the active tab. On the default settings (local embeddings) the article text does not leave your machine - translation, when the page needs it, also runs locally via the browser's own built-in translator, regardless of embedding provider. Telemetry is opt-in and off by default.
Full policy: https://actually-api.sofiaseremeteva.workers.dev/privacy
Status
The extension is live on the
Chrome Web Store.
actually-mcp-server is published on npm and listed in the official MCP
registry.
Redeeming a resolved position is in testing: builder authentication, neg-risk contract selection and the zero-balance guard are each verified against live services, but no redeem has yet been observed collecting funds end to end.
Viewing odds works everywhere. Opening new positions follows Polymarket's own restrictions: it is unavailable in, among others, the US, the UK, France, Germany, Italy, the Netherlands, Belgium, Poland, Ireland, Australia, New Zealand, Japan, Singapore, Taiwan, Thailand, Brazil, Russia, and the Canadian provinces of Ontario, British Columbia, Alberta and Quebec - there, existing positions can still be sold and resting orders cancelled. Sanctioned jurisdictions are blocked entirely. The check runs on the Worker.
Actually does not provide financial advice.
Polymarket tool directories
PolyMart: a directory of Polymarket tools.
Prediction Market Tools: a directory of prediction market projects.
PredAtlas: Actually's profile in a directory of prediction market tools.
License
See LICENSE.
Available Tools
2 toolscheck_newsCheck news text against prediction marketsARead-only
Map a piece of news text to the relevant Polymarket market and return its current YES probability - the market's real, unmodified price, not a number synthesized from the text. That price is the crowd's current bet, not a verdict on whether the news is true. It also does not classify whether the news is dramatized or accurate relative to the market - that interpretation is left to the calling agent, which has both the original text and this market anchor. The probability comes from a precomputed cache refreshed on a cron cadence (can be up to ~2 hours stale) - for a live price before trading, call get_market with the returned marketId. If that cache looks abandoned rather than just late, the response adds cacheStale: true and cacheAgeHours - treat the match as unreliable and prefer get_market/a direct search when present.
Inputs: text (required).
get_marketGet a market's price and orderbookARead-only
Look up a specific Polymarket market by id: details, live price, and an orderbook snapshot for ONE outcome token. Falls back to a direct Gamma lookup when the id is outside the precomputed cache's top markets by volume.
Inputs: marketId (required), outcome.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: check_news maps news text to a market and returns a cached probability, while get_market looks up a specific market by id for live details and orderbook. The descriptions explicitly direct the agent to call get_market for a live price, avoiding overlap.
Both tools follow a consistent verb_noun snake_case pattern (check_news, get_market), making the naming predictable and easy to parse.
Only two tools are provided, which feels thin for a server that could support broader market exploration (e.g., search, listing). However, they cover the core workflow, so it's borderline rather than severely mismatched.
The surface covers news-to-market mapping and single-market live lookup, but lacks operations like searching markets by keyword, listing multiple outcomes, or retrieving orderbooks for all outcomes. These gaps limit an agent's ability to explore beyond the provided news anchor.
Maintenance
Related MCP Connectors
Polymarket in your AI: market rules, real fill costs, who is trading, top traders. Read-only.
Live Polymarket odds, order books, fee-inclusive quotes and non-custodial prediction trading.
Calibrated world model for AI agents. 40 tools: world state, markets, trading. Kalshi + Polymarket.
Trade Polymarket prediction markets from your Ask Gina wallet. Moves real funds.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceEnables interaction with Polymarket prediction markets through read-only access to market data, events, orderbooks, and user positions, plus authenticated trading capabilities for creating and managing orders.1-
- AlicenseNot gradedqualityDmaintenanceEnables real-time access to Polymarket prediction market odds, allowing AI agents to retrieve events, markets, and search for predictions with formatted outputs.5MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with Polymarket prediction markets, including retrieving market data, user positions, and trading history.821 npm12Apache 2.0
- AlicenseBqualityDmaintenanceEnables LLM agents to interact with Polymarket prediction markets, including market discovery, real-time pricing, analytics, account management, and trading with built-in safety guards.34MIT