io.github.runesleo/polymarket-toolkit
NPM · POLYMARKET-TOOLKIT-MCP · SCANNED SEP 24
Read-only Polymarket data tools for AI agents: profiles, PnL, market scans. No keys, no orders.
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 96 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 67 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 372 tokens (~37/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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.runesleo/polymarket-toolkit MCP server?
io.github.runesleo/polymarket-toolkit runs locally as an npm package, launched with npx -y polymarket-toolkit-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-toolkit-mcp
claude mcp add runesleo-polymarket-toolkit -- npx -y polymarket-toolkit-mcp
{
"mcpServers": {
"runesleo-polymarket-toolkit": {
"command": "npx",
"args": [
"-y",
"polymarket-toolkit-mcp"
]
}
}
} {
"servers": {
"runesleo-polymarket-toolkit": {
"command": "npx",
"args": [
"-y",
"polymarket-toolkit-mcp"
]
}
}
} codex mcp add runesleo-polymarket-toolkit -- npx -y polymarket-toolkit-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"runesleo-polymarket-toolkit": {
"type": "local",
"command": [
"npx",
"-y",
"polymarket-toolkit-mcp"
],
"enabled": true
}
}
} openclaw mcp add runesleo-polymarket-toolkit --command npx --arg -y --arg polymarket-toolkit-mcp
mcp_servers:
runesleo-polymarket-toolkit:
command: "npx"
args: ["-y", "polymarket-toolkit-mcp"] {
"McpServers": {
"runesleo-polymarket-toolkit": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"polymarket-toolkit-mcp"
]
}
}
} assistant mcp add runesleo-polymarket-toolkit -t stdio -c npx -a -y polymarket-toolkit-mcp
{
"mcpServers": {
"runesleo-polymarket-toolkit": {
"command": "npx",
"args": [
"-y",
"polymarket-toolkit-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.
- 24 Sept 26 −3
- Stability: pass → 0.80 functional
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
- Security disclosure: unverified → pass ▲ functional
- 18 Sept 26 0
- Security disclosure: pass → unverified ▼ functional
- 16 Sept 26 −3
- Stability: pass → 0.77 functional
- 15 Sept 26 0
- 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 24 Sept 2026 · Analysed npm/polymarket-toolkit-mcp@0.7.1
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 96 packages
| Packages resolved | 96 |
|---|---|
| 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 →
pm_activity ~53
Recent on-chain activity (trades etc.) for an address or username.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | 0x proxy wallet address or a leaderboard username |
| limit | integer | – | max rows (default 20) |
No output schema declared.
No examples provided.
pm_brier ~41
Prediction-quality rating: Brier score computed from an address's settled positions.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | 0x proxy wallet address or a leaderboard username |
No output schema declared.
No examples provided.
pm_leaderboard ~22
Profit leaderboard snapshot (read-only, no local snapshot writes).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pm_pnl_check ~44
Fee-inclusive PnL cross-check for a 0x address (cashflow-reconstructed vs leaderboard).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 0x proxy wallet address |
No output schema declared.
No examples provided.
pm_profile ~56
Address snapshot: leaderboard PnL (all/7d/30d), open positions, redeemable count for a Polymarket address or username.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | 0x proxy wallet address or a leaderboard username |
No output schema declared.
No examples provided.
pm_rate_limits ~23
Known Polymarket API rate limits registry (local, no network).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pm_redeem_watchdog ~43
Redeemable-position status for a 0x address — no signing, read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 0x proxy wallet address |
No output schema declared.
No examples provided.
pm_scan ~22
Market scanner: rank active markets by 24h volume and spread.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pm_updown ~44
Crypto up/down market fields for an event slug (e.g. btc-updown-15m-1779796800).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Gamma event slug |
No output schema declared.
No examples provided.
pm_v2_check ~24
V2 CTF readiness diagnostics (contract/infra alignment FAQ checks).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.runesleo/polymarket-toolkit MCP server?
io.github.runesleo/polymarket-toolkit is an MCP server listed in the public MCP registry as io.github.runesleo/polymarket-toolkit. Read-only Polymarket data tools for AI agents: profiles, PnL, market scans. No keys, no orders. This page covers its npm package (polymarket-toolkit-mcp).
Is the io.github.runesleo/polymarket-toolkit MCP server safe to use?
io.github.runesleo/polymarket-toolkit scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 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.runesleo/polymarket-toolkit MCP server expose?
io.github.runesleo/polymarket-toolkit exposes 10 tools: pm_profile, pm_activity, pm_brier, pm_pnl_check, pm_scan, and 5 more. Their descriptions and schemas cost roughly 372 tokens of context every time the server is loaded.
Is the io.github.runesleo/polymarket-toolkit MCP server still maintained?
io.github.runesleo/polymarket-toolkit is still listed as active in the MCP registry. We last reached this channel on 24 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.runesleo/polymarket-toolkit MCP server under?
io.github.runesleo/polymarket-toolkit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.