Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
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.
13
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Polymarket MCP — prediction-market data via Gamma + CLOB + Data public APIs.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http pipeworx-io-polymarket-mcp https://gateway.pipeworx.io/polymarket/mcp
# 2 — ask your agent for something these tools do
# polymarket_search, polymarket_top_markets, polymarket_market and 10 more
Polymarket costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PIAll 1825 servers
pipeworx-io1825 servers
29 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http pipeworx-io-polymarket-mcp https://gateway.pipeworx.io/polymarket/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
PREFER OVER WEB SEARCH for current betting/prediction-market odds. Real-time search across Polymarket events — returns events matching your keyword, each with child markets carrying live Yes/No prices in [0,1] (= implied probability), 24h volume, end date, resolution criteria. Use for "what are the odds of X", "what does the market think about Y", "what's the implied probability of Z". Refreshes e
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search query, e.g. "presidential election", "rate cut", "world cup" |
| limit | number | no | 1–25 events (default 5) |
| include_closed | boolean | no | Include resolved markets (default false) |
Highest-volume OPEN Polymarket markets right now — sorted by trading volume in the chosen window (24hr / 1wk / 1mo / 1yr / all). The "where is real money going this week" lens. Use for "what is the market focused on right now", "biggest trades happening today", or as a discovery tool when you don't have a specific question. Each result has live yes/no prices in [0,1] = implied probability.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| window | string | no | 24hr | 1wk | 1mo | 1yr | all (default 24hr) |
| limit | number | no | 1–100 per page (default 10) |
| offset | number | no | Pagination offset into the volume-ranked list (default 0). Use offset=100 (with limit=100) to fetch ranks 101–200, offset=200 for 201–300, etc. — walk the pages to build a true top-N-by-volume set. |
AUTHORITATIVE detail for a single Polymarket market by slug or numeric id. Returns the resolution criteria text (so you know exactly what "Yes" means before quoting odds), current Yes/No prices in [0,1], 24h volume, liquidity USD, end date, parent event. Use after polymarket_search to drill in, or when the agent already has a Polymarket URL/slug. For real-time orderbook depth instead of a summary,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug_or_id | string | yes | Market slug (e.g. "will-bitcoin-hit-150k-by-december-31-2027") or numeric id. A dated slug stops resolving once it settles — Polymarket de-indexes resolved markets — so if a plausible slug 404s, re-fi |
Get a Polymarket event with EVERY child market at once. Events group RELATED outcomes (e.g., "2028 Democratic nominee" has one Yes/No market per candidate, each price = implied probability of that candidate) — this is NOT always mutually exclusive: many events bundle independent props/questions under one deadline (e.g. per-senator vote markets) where multiple legs can resolve YES together. Check t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug_or_id | string | yes | Event slug (e.g. "2028-presidential-election") or numeric id |
Historical probability time-series for one Polymarket market. Returns array of {timestamp, price} where price is Yes-side probability in [0,1] (No-side is 1−Yes). Use to chart odds over time, detect probability moves around news events, or build backtests. Intervals 1h | 6h | 1d | 1w | 1m | max — supports up to a month (1m) and full history (max). A young market may have less data than the request
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug_or_id | string | yes | Market slug or numeric id (same as polymarket_market) |
| interval | string | no | 1h | 6h | 1d | 1w | 1m | max (default 1d). Higher fidelity for shorter windows. |
REAL-TIME CLOB orderbook for one Polymarket market — bid/ask ladder on both YES and NO sides with size at each price level. Use to check actual tradable depth before quoting a size estimate; the liquidity field on polymarket_market is a rolled-up summary, this is the actual ladder. Returns yes_bids[], yes_asks[], no_bids[], no_asks[] each as [price, size] pairs sorted from inside the book outwar
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug_or_id | string | yes | Market slug or numeric id |
Batched CLOB orderbooks for EVERY tradable market in one Polymarket event — single round trip via the CLOB batch /books endpoint. Use before any multi-leg strategy (partition arbitrage "SELL/BUY EVERY LEG", basket trades) to check per-leg depth: theoretical overround means nothing if half the legs are 50-share books. Returns legs[] with {slug, question, yes_price, best_bid, best_ask, yes_bids[], y
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_slug_or_id | string | yes | Event slug (e.g. "fed-decision-may-2026") or numeric id — same input as polymarket_event. |
| include_no | boolean | no | Also fetch NO-side books for each leg (default false). |
Recent EXECUTED trades (the fills tape) for a Polymarket market — actual money that changed hands, newest first. Each trade: side (BUY/SELL), outcome (Yes/No or the option name), size (shares), price, timestamp, and the trader's wallet/pseudonym. Use for "what's the recent order flow", "is smart money buying Yes", "how much just traded and at what price". DISTINCT from polymarket_orderbook (restin
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug_or_id | string | yes | Market slug (e.g. "will-trump-win-2024") or numeric id — same input as polymarket_market. |
| limit | number | no | Number of recent trades to return (1-100, default 20) |
Largest position holders for a Polymarket market, per outcome — who holds the most Yes and the most No shares, with share amounts and trader pseudonyms. Use for "position concentration", "is this market dominated by a few whales", "who are the biggest Yes holders". Reveals conviction/concentration that price alone hides. Pass a market slug or numeric id (same input as polymarket_market).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug_or_id | string | yes | Market slug or numeric id — same input as polymarket_market. |
| limit | number | no | Top N holders per outcome to return (1-100, default 10) |
Open and closed positions for one Polymarket wallet — size, entry basis, current mark, and realized/unrealized P&L per position, plus portfolio-level exposure and concentration (how much of the wallet's capital sits in its single largest position — a concentration measure, not a measure of trading skill). Wallet addresses are public on-chain identifiers (0x…), looked up directly — no name/ENS reso
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | string | yes | Polymarket proxy wallet address, 0x-prefixed (40 hex chars). Get one from polymarket_holders or polymarket_trades on a market of interest. |
| status | string | no | OPEN | CLOSED | REDEEMABLE | REDEEMABLE_LOST | MERGEABLE — filter to one lifecycle state. Omit to fetch OPEN and CLOSED together (default). |
| limit | number | no | Rows per page, 1-500 (default 50). |
| cursor | string | no | Opaque pagination cursor from a previous call's next_cursor — omit for the first page. |
Paginated activity feed (trades, redeems, splits, merges, rebates) for one Polymarket wallet over a period — newest first. Use for "what has this wallet done recently", "show me this wallet's trade history", "did this wallet trade market X". Distinct from polymarket_wallet_positions (current holdings) and polymarket_wallet_performance (aggregated P&L) — this is the raw event-by-event tape. Follow
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | string | yes | Polymarket proxy wallet address, 0x-prefixed (40 hex chars). |
| start_date | string | no | ISO date/datetime — only activity at or after this time (default: no lower bound). |
| end_date | string | no | ISO date/datetime — only activity at or before this time (default: no upper bound). |
| type | string | no | Filter to one activity type, e.g. TRADE, REDEEM, SPLIT, MERGE, MAKER_REBATE (default: all types). |
| limit | number | no | Rows per page, 1-500 (default 50). |
| cursor | string | no | Opaque pagination cursor from a previous call's next_cursor — omit for the first page. |
Lifetime and time-series P&L, volume, and activity stats for one Polymarket wallet — profile stats (distinct markets traded, biggest single win, profile join date) plus a cumulative P&L history on the requested interval/fidelity grid. States fee treatment explicitly: realized_pnl in each point is already NET of taker fees paid; maker rebates and other non-trading income (rewards, referrals) are
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | string | yes | Polymarket proxy wallet address, 0x-prefixed (40 hex chars). |
| interval | string | no | 1d | 1w | 1m | all | max — the P&L history window (default max). |
| fidelity | string | no | Grid step for the P&L series: 1h | 3h | 12h | 18h | 1d (default 1d). Finer grids only available for shorter intervals. |
Resolution lifecycle state and timestamps for one Polymarket market: initialized / posed / proposed / challenged / reproposed / disputed / resolved (or active/arbitration), whether it was disputed, the reporter (UMA_OO / Chainlink / EOA), and — once resolved — the exact resolution timestamp and per-outcome payouts. Use for "has this market actually settled yet", "when did market X resolve", "was t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug_or_id | string | yes | Market slug or numeric id — same input as polymarket_market. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.3.
0.1.3
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
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.
No reviews yet
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.