Polymarket Us
NPM · @PIPEWORX/MCP-POLYMARKET-US · 2 COMPONENTS
Polymarket US MCP — market data for Polymarket US (polymarket.us), the CFTC-regulated, US-licensed…
Available components
Last scanned (6 hours ago)
Scores higher than 65% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-polymarket-us). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1078 tokens (~215/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-polymarket-us@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-polymarket-us |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-polymarket-us/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3691853404 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:62008576a6f757c73c1d14dc8ffb0909080e1dff427a71df312665d6e36f18477756edeac4fe30fabdf07f3a7915ab75a09793cc18a1c5632786f936d |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
polymarket_us_bbo ~140
Best bid/offer (lightweight top-of-book) for one Polymarket US market by slug — current price, last trade price, best bid, best ask, bid/ask depth (number of price levels), open interest, shares traded, and market state. Use before quoting a price when you need just the top of book, not the full depth ladder (for that, see polymarket_us_book). Get a slug from polymarket_us_search.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Polymarket US market slug (e.g. "aec-nfl-lac-ten-2025-11-02"), from polymarket_us_search. |
No output schema declared.
No examples provided.
polymarket_us_book ~113
Full order book (bid/ask depth ladder with size at every visible price level) plus session stats — open/high/low/last-trade price, shares traded, notional traded, open interest — for one Polymarket US market by slug. Use to check actual tradable depth before sizing a trade; polymarket_us_bbo gives only the top of book. Get a slug from polymarket_us_search.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Polymarket US market slug, from polymarket_us_search. |
No output schema declared.
No examples provided.
polymarket_us_price_history ~219
Historical Yes/No display-price time series for one Polymarket US market by slug. `interval` picks a fixed lookback window (1h | 6h | 1d | 1w | 1m | all); `fidelity` is the spacing between points in minutes (default 60). Returns an array of {timestamp, yes_price, no_price} — these are DISPLAY prices (yes normally derived from the best ask, no from one minus the best bid) and preserve the bid/ask spread, so yes_price + no_price can exceed 1.0 — that is not a data error. Get a slug from polymarket_us_search.
| Name | Type | Req | Description |
|---|---|---|---|
| fidelity | number | – | Minutes between data points, minimum 1 (default 60). |
| interval | string | – | 1h | 6h | 1d | 1w | 1m | all (default 1d) |
| slug | string | yes | Polymarket US market slug, from polymarket_us_search. |
No output schema declared.
No examples provided.
polymarket_us_search ~340
Market search/discovery on Polymarket US (polymarket.us) — the SEPARATE, CFTC-regulated, US-licensed venue, distinct from the offshore `polymarket` pack and from `kalshi`. Pass `query` for a keyword search across the full market corpus (returns matching events, each with its child markets and live prices). Omit `query` to BROWSE instead — the highest-volume open markets right now, optionally filtered by `category` (e.g. "macro", "sports", "politics"). Use for "what does Polymarket US have on X", "biggest markets trading right now on the regulated US venue", or as a first step before polymarket_us_bbo / polymarket_us_book / polymarket_us_price_history / polymarket_us_settlement, all of which need a market `slug` this tool returns. Every market price is YES-side implied probability in [0,1].
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Browse-only filter, e.g. "macro", "sports", "politics", "crypto". Ignored when `query` is set (Polymarket US search has no category filter). |
| limit | number | – | 1–50 results (default 10) |
| query | string | – | Keyword search, e.g. "fed rate", "election", "nfl". Omit to browse the highest-volume open markets instead. |
| status | string | – | open | closed (default open). With a query, filters the search; without one, "open" means active & not closed, "closed" means closed. |
No output schema declared.
No examples provided.
polymarket_us_settlement ~211
Settlement (resolution) result for one Polymarket US market by slug — the final settlement price, which is 1 for the winning side / 0 for the losing side on a binary market (and can be a fractional value for a 50/50 or partial settlement). Three distinguishable outcomes: a settled market returns `settled: true` with the price; an open market that exists but has not resolved returns `settled: false` with no price and a "still open" message; a slug that does not exist on Polymarket US returns `error: "not_found"` with `settled: null` — it is NEVER reported as "still open". Use after polymarket_us_search / a known slug to check how a market actually resolved. NOTE: this tool returns a price only, no settlement timestamp — Polymarket US does not publish one on this endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Polymarket US market slug, from polymarket_us_search. |
No output schema declared.
No examples provided.
How do I install the Polymarket Us MCP server?
Polymarket Us runs locally as an npm package, launched with npx -y @pipeworx/mcp-polymarket-us. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-polymarket-us
claude mcp add pipeworx-io-polymarket-us -- npx -y @pipeworx/mcp-polymarket-us
What is the Polymarket Us MCP server?
Polymarket Us is an MCP server listed in the public MCP registry as io.github.pipeworx-io/polymarket-us. Polymarket US MCP, market data for Polymarket US (polymarket.us), the CFTC-regulated, US-licensed… This page covers its npm package (@pipeworx/mcp-polymarket-us).
Is the Polymarket Us MCP server safe to use?
Polymarket Us scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Polymarket Us MCP server expose?
Polymarket Us exposes 5 tools: polymarket_us_search, polymarket_us_bbo, polymarket_us_book, polymarket_us_price_history, polymarket_us_settlement. Their descriptions and schemas cost roughly 1,023 tokens of context every time the server is loaded.
Is the Polymarket Us MCP server still maintained?
Polymarket Us is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Polymarket Us MCP server under?
Polymarket Us declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.