io.github.evidai/polymarket-guard
NPM · POLYMARKET-GUARD-MCP · SCANNED SEP 21
Polymarket prediction markets — buy/sell positions in USDC. LemonCake pay-per-call billing.
Available components
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 Security98
- 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
- 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 121 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1091 tokens (~99/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
How do I install the io.github.evidai/polymarket-guard MCP server?
io.github.evidai/polymarket-guard runs locally as an npm package, launched with npx -y polymarket-guard-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · polymarket-guard-mcp
claude mcp add evidai-polymarket-guard -- npx -y polymarket-guard-mcp
{
"mcpServers": {
"evidai-polymarket-guard": {
"command": "npx",
"args": [
"-y",
"polymarket-guard-mcp"
]
}
}
} {
"servers": {
"evidai-polymarket-guard": {
"command": "npx",
"args": [
"-y",
"polymarket-guard-mcp"
]
}
}
} codex mcp add evidai-polymarket-guard -- npx -y polymarket-guard-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"evidai-polymarket-guard": {
"type": "local",
"command": [
"npx",
"-y",
"polymarket-guard-mcp"
],
"enabled": true
}
}
} openclaw mcp add evidai-polymarket-guard --command npx --arg -y --arg polymarket-guard-mcp
mcp_servers:
evidai-polymarket-guard:
command: "npx"
args: ["-y", "polymarket-guard-mcp"] {
"McpServers": {
"evidai-polymarket-guard": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"polymarket-guard-mcp"
]
}
}
} assistant mcp add evidai-polymarket-guard -t stdio -c npx -a -y polymarket-guard-mcp
{
"mcpServers": {
"evidai-polymarket-guard": {
"command": "npx",
"args": [
"-y",
"polymarket-guard-mcp"
]
}
}
} 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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
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 21 Sept 2026 · Analysed npm/polymarket-guard-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| 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 →
cancel_order ~58
Cancel an open limit order by order ID. Requires POLYMARKET_PRIVATE_KEY. Billed at $0.10 USDC via LemonCake.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The order ID returned by place_limit_order or get_trade_history |
No output schema declared.
No examples provided.
get_balance ~45
Get your USDC balance and token allowances on Polymarket's Polygon contracts. Requires POLYMARKET_PRIVATE_KEY. Billed at $0.05 USDC via LemonCake.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_market ~60
Get full details for a single Polymarket market by its condition ID or slug. Includes resolution criteria, outcomes, current prices, and volume. Free — no billing.
| Name | Type | Req | Description |
|---|---|---|---|
| condition_id | string | yes | Market condition ID (hex string) or market slug |
No output schema declared.
No examples provided.
get_order_book ~67
Get the live order book (bids and asks) for a Polymarket market token. Use token_id from list_markets or get_market. Free — no billing.
| Name | Type | Req | Description |
|---|---|---|---|
| token_id | string | yes | The token ID for a specific outcome (YES or NO) from get_market |
No output schema declared.
No examples provided.
get_positions ~78
Get your current open positions on Polymarket: market titles, outcome tokens, shares held, cost basis, and current P&L. Requires POLYMARKET_PRIVATE_KEY. Billed at $0.05 USDC via LemonCake.
| Name | Type | Req | Description |
|---|---|---|---|
| size_threshold | number | – | Only return positions larger than this (default 0 = all positions) |
No output schema declared.
No examples provided.
get_trade_history ~81
Get your past trades on Polymarket: order IDs, market, outcome, price, size, timestamp. Requires POLYMARKET_PRIVATE_KEY. Billed at $0.05 USDC via LemonCake.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of trades to return (default 20, max 100) |
| offset | number | – | Pagination offset |
No output schema declared.
No examples provided.
list_markets ~96
List active Polymarket prediction markets. Returns market titles, condition IDs, token IDs, volume, and YES/NO prices. Free — no billing.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max markets to return (default 20, max 100) |
| offset | number | – | Pagination offset (default 0) |
| tag | string | – | Filter by tag/category, e.g. 'politics', 'crypto', 'sports' |
No output schema declared.
No examples provided.
place_limit_order ~162
Place a limit order to buy or sell outcome shares at a specific price on Polymarket CLOB. Requires POLYMARKET_PRIVATE_KEY. Billed at $0.10 USDC via LemonCake.
| Name | Type | Req | Description |
|---|---|---|---|
| expiration | string | – | Order time-in-force: GTC=Good Till Cancel (default), GTD=till date, FOK=Fill or Kill, IOC=Immediate or Cancel |
| price | number | yes | Limit price (0–1, representing probability/cents per share). E.g. 0.65 = 65 cents. |
| side | string | yes | – |
| size | number | yes | Number of shares to buy or sell |
| token_id | string | yes | Outcome token ID (YES or NO) from get_market |
No output schema declared.
No examples provided.
place_market_order ~139
Buy or sell outcome shares at market price on Polymarket. USDC cost is calculated at the current best ask/bid. Requires POLYMARKET_PRIVATE_KEY. Billed at $0.10 USDC via LemonCake.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | USDC amount to spend (BUY) or number of shares to sell (SELL) |
| side | string | yes | BUY outcome shares or SELL shares you hold |
| slippage_tolerance | number | – | Max acceptable slippage as a decimal (default 0.02 = 2%) |
| token_id | string | yes | Outcome token ID from get_market (YES or NO token) |
No output schema declared.
No examples provided.
redeem_positions ~71
Claim winnings from resolved Polymarket markets. Redeems outcome token shares for USDC if the market resolved in your favor. Requires POLYMARKET_PRIVATE_KEY. Billed at $0.10 USDC via LemonCake.
| Name | Type | Req | Description |
|---|---|---|---|
| condition_id | string | yes | Condition ID of the resolved market to redeem from |
No output schema declared.
No examples provided.
search_markets ~66
Search Polymarket markets by keyword. Searches market titles and descriptions. Free — no billing.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 20, max 100) |
| query | string | yes | Search keyword(s), e.g. 'bitcoin ETF', 'US election' |
No output schema declared.
No examples provided.
What is the io.github.evidai/polymarket-guard MCP server?
io.github.evidai/polymarket-guard is an MCP server listed in the public MCP registry as io.github.evidai/polymarket-guard. Polymarket prediction markets, buy/sell positions in USDC. LemonCake pay-per-call billing. This page covers its npm package (polymarket-guard-mcp).
Is the io.github.evidai/polymarket-guard MCP server safe to use?
io.github.evidai/polymarket-guard scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 io.github.evidai/polymarket-guard MCP server expose?
io.github.evidai/polymarket-guard exposes 11 tools: list_markets, search_markets, get_market, get_order_book, get_positions, and 6 more. Their descriptions and schemas cost roughly 923 tokens of context every time the server is loaded.
Is the io.github.evidai/polymarket-guard MCP server still maintained?
io.github.evidai/polymarket-guard is still listed as active in the MCP registry. We last reached this channel on 21 September 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 io.github.evidai/polymarket-guard MCP server under?
io.github.evidai/polymarket-guard declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.