Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Prediction Market Intelligence 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.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Polymarket in your AI: market rules, real fill costs, who is trading, top traders. Read-only.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http prediction-market-intelligence-mcp https://mcp.lacuna.markets/mcp
# 2 — ask your agent for something these tools do
# pm_search, pm_market, pm_book and 4 more
Prediction Market Intelligence costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LAAll 1 server
lacuna1 server
1 category
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 prediction-market-intelligence-mcp https://mcp.lacuna.markets/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
7 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.
Use this first when the user asks what Polymarket thinks about a topic, how likely something is, or names a market without a link. Searches every Polymarket market by keyword (Polymarket's own full-text search) or by a polymarket.com link and returns events with all their outcomes, current prices, 24h volume and end dates, plus the slug to pass to the other tools. Use status='resolved' for past ma
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Keywords ("fed october", "bitcoin 150k", "house 2026") or a polymarket.com link. |
| status | string | no | open (default), resolved, or all. |
| limit | integer | no | Number of events to return (1–10, default 5). |
Use this when the user asks about one Polymarket market or event: its price, what exactly decides how it resolves, whether an outcome has been proposed or disputed, when it ends, its fees, or how it has moved. Returns prices, bid/ask and spread, change over 1h/24h/7d/30d with a 30-day range, volume and liquidity, taker fees, the resolution rules verbatim with their named source, and the live resol
| Parameter | Type | Required | Notes |
|---|---|---|---|
| market | string | yes | A polymarket.com link, or a market or event slug from pm_search. |
| outcome | string | no | For a multi-outcome event: the outcome label to show in detail ("25 bps decrease"). |
Use this when the user asks how liquid a Polymarket market is, how much a trade of a given size would really cost, how far it would move the price, or what the order book looks like. Returns the live book for one outcome: best levels, spread, dollar depth near the mid and which side is heavier. With amount it walks the book level by level for a market order (dollars to spend when buying, shares wh
| Parameter | Type | Required | Notes |
|---|---|---|---|
| market | string | yes | A polymarket.com link, or a market or event slug from pm_search. |
| outcome | string | no | Which outcome: "Yes"/"No", a team name, or for a multi-outcome event the outcome label ("25 bps decrease"). Default: the first outcome (usually Yes). |
| side | string | no | buy (default) or sell. |
| amount | number | no | For buy: dollars to spend. For sell: number of shares to sell. Omit to see the book only. |
Use this when the user asks who is buying or selling a Polymarket market, why its price moved, where the money is going, who the biggest holders are, or (with no market) what the whales are doing across Polymarket. For a market or event: dollars traded and net direction per outcome, distinct wallets, the largest trades, the wallets that moved the most money, and for a single market the biggest cur
| Parameter | Type | Required | Notes |
|---|---|---|---|
| market | string | no | A polymarket.com link, or a market or event slug from pm_search. Omit to see the largest trades across all of Polymarket. |
| hours | integer | no | Look-back window in hours (1–168, default 24). |
| outcome | string | no | For a multi-outcome event: limit to one outcome by its label. |
| min_usd | number | no | Without a market: only trades of at least this many dollars (default $10,000). |
Use this when the user asks what is moving, trending or changing on Polymarket, what moved overnight or this week, or for the biggest gainers and losers. Ranks the 300 most-traded open markets by price change over the last hour, day, week or month, with old and current price, the move in percentage points, 24h volume and the slug for follow-ups (pm_flow shows who moved it). Markets that are merely
| Parameter | Type | Required | Notes |
|---|---|---|---|
| window | string | no | Look-back window: 1h, 24h (default), 7d or 30d. |
| direction | string | no | both (default), up only, or down only. |
| min_volume_24h_usd | number | no | Skip markets that traded less than this in the last 24h (default $10,000). |
| include_games | boolean | no | Include individual sports games, whose prices move with the score (default false). |
| limit | integer | no | Rows to return (1–20, default 10). |
Use this when the user asks who the best or biggest Polymarket traders are, who made the most money today, this week, this month or all time, or who leads in a category (politics, sports, crypto, economics, finance, culture, tech, weather, mentions). Returns Polymarket's own leaderboard ranked by profit or by volume, with usernames and wallet addresses to pass to pm_portfolio.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| period | string | no | day, week (default), month or all. |
| by | string | no | Rank by profit and loss (pnl, default) or by dollar volume. |
| category | string | no | overall (default) or one category. |
| limit | integer | no | Rows to return (1–25, default 10). |
Use this when the user asks what a Polymarket trader or wallet holds, how good a trader is, or wants to size up a wallet seen in pm_flow. Returns the track record (all-time and 30-day profit and loss, volume, leaderboard rank, markets traded), open positions with entry and current price, unrealized P&L, exposure grouped by event, settled winnings not yet redeemed, and recent trades. Accepts a 0x w
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | string | yes | 0x wallet address, polymarket.com profile link (…/@name or …/profile/0x…), or Polymarket username. |
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 Prediction Market Intelligence 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. 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 1.0.0.
1.0.0
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 Prediction Market Intelligence 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.