Model Context Protocol (MCP) server for freee API integration
Polymarket is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Polymarket market data, live CLOB books, replay, simulation, and opt-in trading in Rust.
Quickstart
This one is not published to a package registry, so there is no one-line install: it is built and started the way its own source says.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Polymarket as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This one is not published to a package registry, so there is no one-line install: it is built and started the way its own source says.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Report this server's version, operating mode, database, and configured Polymarket API endpoints. This tool makes no network request.
No parameter schema on file.
Search active Polymarket events and return matching markets with IDs, outcome token mappings, prices, liquidity, and 24-hour volume.
No parameter schema on file.
Get one market by its Gamma market ID, including outcome token IDs and current CLOB V2 order-book summaries when the market is open.
No parameter schema on file.
Build one answer-ready, source-linked market brief from a market ID, slug, or condition ID. Combines current metadata, exact executable books, microstructure, bounded price history, sample fill impact, timestamps, and limitations. Prefer this for a complete market explanation.
No parameter schema on file.
List active open Polymarket markets with stable market-level ranking and pagination plus topic, featured, liquidity, volume, and end-time filters. Prefer this over text search for scans and rankings.
No parameter schema on file.
Get an event by Gamma event ID or slug, including metadata, tags, and all related markets with outcome-token mappings.
No parameter schema on file.
Analyze an event-level mutually exclusive/exhaustive basket only when Gamma explicitly marks the event negative-risk. Sums executable Yes bids/asks, reports top-level capacity and gross edge, and refuses to infer logical relationships from text alone. Descriptive only; never places an order.
No parameter schema on file.
Get a current CLOB V2 order book by outcome token ID, including exact bid/ask levels, spread, midpoint, tick size, and feed timestamp.
No parameter schema on file.
Compute exact-decimal L2 microstructure metrics for one outcome token: spread, midpoint, microprice, top-level and aggregate imbalance, depth, near-touch liquidity, and two-sided sample execution impact. Descriptive only; never places an order.
No parameter schema on file.
Scan up to 20 high-volume active markets concurrently and return compact per-outcome L2 microstructure, sample execution impact, and binary-market complement checks. Public read-only analysis; never places an order.
No parameter schema on file.
Get bounded public historical prices for one CLOB outcome token using a preset interval or explicit Unix timestamp range.
No parameter schema on file.
Get the largest public holders for each outcome token in a market, identified by its 0x-prefixed condition ID.
No parameter schema on file.
Compare two to ten markets using the same current metadata, outcome prices, liquidity, volume, and CLOB order-book metrics.
No parameter schema on file.
Get current open positions and P/L fields for a public Polymarket proxy-wallet address. No credentials are required.
No parameter schema on file.
Get the current total pUSD value of open positions for a public Polymarket proxy wallet.
No parameter schema on file.
Get public executed-trade history for a Polymarket proxy wallet, with exact token IDs, prices, sizes, sides, and transaction hashes.
No parameter schema on file.
Get public on-chain wallet activity including trades, splits, merges, redemptions, rewards, and conversions.
No parameter schema on file.
Compute transparent exposure, P/L, concentration, redeemability, and negative-risk summaries from a wallet's public open positions. Descriptive only; not financial advice.
No parameter schema on file.
Build one source-linked summary for a public Polymarket proxy wallet: open positions, current value, transparent concentration and P/L metrics, recent trades, recent activity, timestamps, and limitations. No credentials are required.
No parameter schema on file.
Start a persistent public CLOB websocket watch for one to fifty outcome token IDs. Returns immediately with a watch ID while Rust maintains full books in the background.
No parameter schema on file.
Read compact current order-book snapshots from a background watch, including upstream and local timestamps, feed age, update counts, and errors.
No parameter schema on file.
Report websocket connection state, active subscriptions, update counts, feed timestamps, and the most recent error for every watch.
No parameter schema on file.
Read sequenced trade, best-bid/ask, tick-size, new-market, and resolution events retained for an active watch.
No parameter schema on file.
Stop and remove a background market-data watch. Safe and idempotent; stopped is false when the watch no longer exists.
No parameter schema on file.
Persist a watch's initial full books and subsequent websocket updates to SQLite. Returns a recording ID; dropped broadcast updates are counted explicitly.
No parameter schema on file.
Flush and stop an active SQLite recording, returning final snapshot and dropped-update counts.
No parameter schema on file.
List local SQLite recordings with token coverage, lifecycle timestamps, snapshot counts, and any detected dropped updates.
No parameter schema on file.
Replay locally recorded full-book states in deterministic upstream-timestamp order, optionally filtered by token and time range.
No parameter schema on file.
Replay sequenced trades, best-price changes, tick-size changes, new-market notices, and resolutions persisted by a local recording. This returns captured observations, not complete exchange history.
No parameter schema on file.
Walk the current public CLOB book to estimate fill, notional, average/worst price, and slippage for a buy or sell in outcome shares. Never places an order.
No parameter schema on file.
Report whether trading is explicitly enabled, whether a signer is configured, the signer address, the pUSD order cap, and the confirmation model. Never authenticates or trades.
No parameter schema on file.
Apply local decimal and notional policy checks to a limit or market order, fetch current tick/minimum rules by default, then issue a single-use five-minute approval. This does not guarantee exchange acceptance or a fill and never places an order.
No parameter schema on file.
Read the durable lifecycle and result of an order approval, including ambiguous submission failures.
No parameter schema on file.
Consume a fresh single-use approval and place its exact signed order. Requires POLYMARKET_ENABLE_TRADING=true, a private key, and confirm=true.
No parameter schema on file.
Atomically submit one to ten fresh approved orders. The batch total shares the configured notional cap and requires the exact confirmation PLACE_BATCH.
No parameter schema on file.
Get one authenticated account order by order ID.
No parameter schema on file.
List the authenticated account's open orders, optionally filtered by outcome token ID.
No parameter schema on file.
List the authenticated account's CLOB trades, optionally filtered by outcome token ID.
No parameter schema on file.
Start an authenticated CLOB WebSocket watch for this account's order and trade events in one to fifty condition IDs. Requires a configured private key but not trading enablement; it never places or cancels an order.
No parameter schema on file.
Read buffered authenticated order and trade events after a watch-local sequence number.
No parameter schema on file.
Report authenticated user-event watches, event counts, and connection errors. This makes no network request.
No parameter schema on file.
Stop one authenticated user-event WebSocket watch. This never cancels exchange orders.
No parameter schema on file.
Get the authenticated account's pUSD collateral or outcome-token balance and contract allowances.
No parameter schema on file.
Cancel one authenticated account order. Requires trading enablement and confirm=true.
No parameter schema on file.
Cancel every authenticated account order. Requires the exact confirmation string CANCEL_ALL.
No parameter schema on file.
Cancel authenticated orders for one condition, outcome token, or both. Requires the exact confirmation CANCEL_MARKET.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Polymarket or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
It installs from its repository rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 0.1.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Polymarket can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.