PMWallets
NPM · PMWALLETS · 3 COMPONENTS
Polymarket smart-money data: rank traders by on-chain PnL, follow them, read their fills.
Available components
Last scanned (9 hours ago)
Scores higher than 38% of npm servers
Category Crypto and Web3
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
- 0 of 6 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- 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 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 959 tokens (~106/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% 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 9 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 15 Oct 26 +29
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 86 functional
- 14 Oct 26 39
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 18 Oct 2026 · Analysed npm/pmwallets@0.6.5
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 6 packages
| Packages resolved | 6 |
|---|---|
| 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 →
account ~19
The account's plan (allowances used) and balance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cancel_subscription ~35
Stop following (and stop paying for) a subscription, by its id from `subscriptions`.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | subscription id |
No output schema declared.
No examples provided.
entity ~53
One trader's statistics by handle or address (full address only once unlocked).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 12-character handle or 0x address |
| period | string | – | "30d" or "7d" |
No output schema declared.
No examples provided.
fills ~73
Fills of the followed traders strictly after a ledger position (block, logIndex), oldest first. Does not move the new_fills cursor.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | max 500 |
| sinceBlock | number | yes | block |
| sinceLogIndex | number | – | log index within the block (default 0) |
No output schema declared.
No examples provided.
leaderboard ~376
Polymarket traders ranked by realized PnL and other stats over a window, with filters. Each row is an entity (one trader, possibly several wallets).
| Name | Type | Req | Description |
|---|---|---|---|
| bands | string | – | unlock price bands to include, comma-separated: 0 = free … 5 |
| category | string | – | market category, e.g. "politics", "sports", "crypto", "crypto-updown", "esports" |
| dir | string | – | – |
| limit | number | – | rows, at most 200 (rows count against a daily allowance of 20,000) |
| maxWallets | number | – | at most this many wallets in the entity |
| minCategoryShare | number | – | with category: at least this share (0–1] of the trader's volume in it |
| minEligible | number | – | floor on markets that count toward the win rate |
| minFills | number | – | floor on number of fills |
| minPnl | number | – | floor on realized PnL in USD |
| minRoi | number | – | floor on ROI on buys (0.1 = 10%) |
| minVolume | number | – | floor on traded volume in USD |
| minWinLo | number | – | floor on the lower bound of the 95% win-rate interval (0–1): a win rate that is not luck |
| minWinsLosses | number | – | floor on markets won or lost |
| offset | number | – | rows to skip (signed-in accounts; anonymous callers see a fixed sample) |
| period | string | – | statistics window: "30d" (default) or "7d" |
| sort | string | – | column to sort by (default realizedPnl) |
| status | string | – | – |
| style | string | – | – |
No output schema declared.
No examples provided.
market ~44
The Polymarket market and outcome an outcome token id belongs to (question, outcome name, slug, end date).
| Name | Type | Req | Description |
|---|---|---|---|
| tokenId | string | yes | outcome token id (decimal) |
No output schema declared.
No examples provided.
new_fills ~103
Fills of the followed traders since the previous call of this tool (first call: the last hour). Each fill is returned once to this server; the CLI `pmwallets new-fills` shares the position file, so do not poll with both at once (or give each its own PMW_MCP_STATE). Call again while `more` is true.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | at most this many fills (default 100, max 500) |
No output schema declared.
No examples provided.
subscribe ~76
Follow a trader: their fills start arriving from now on. BILLS THE ACCOUNT per hour (unless the plan covers it). 402 = balance too low; 409 = no fill for 7 days (retry with acceptInactive).
| Name | Type | Req | Description |
|---|---|---|---|
| acceptInactive | boolean | – | – |
| entityId | string | yes | handle or 0x address |
No output schema declared.
No examples provided.
subscriptions ~18
The traders this account follows (active and paused subscriptions).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the PMWallets MCP server?
PMWallets runs locally as an npm package, launched with npx -y pmwallets. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · pmwallets
claude mcp add polymarketwallets-pmwallets -- npx -y pmwallets
What is the PMWallets MCP server?
PMWallets is an MCP server listed in the public MCP registry as io.github.polymarketwallets/pmwallets. Polymarket smart-money data: rank traders by on-chain PnL, follow them, read their fills. This page covers its npm package (pmwallets).
Is the PMWallets MCP server safe to use?
PMWallets scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 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 PMWallets MCP server expose?
PMWallets exposes 9 tools: leaderboard, entity, subscriptions, subscribe, cancel_subscription, and 4 more. Their descriptions and schemas cost roughly 797 tokens of context every time the server is loaded.
Is the PMWallets MCP server still maintained?
PMWallets is still listed as active in the MCP registry. We last reached this channel on 18 October 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 PMWallets MCP server under?
PMWallets declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.