three.ws KOL
NPM · @THREE-WS/KOL-MCP
Per-wallet KOL deep dive — a tracked trader's portfolio P&L and its trades on a given mint.
Available components
Last scanned (3 hours ago)
Scores higher than 62% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 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 (Apache-2.0).Pass
- Actively maintained (last published 54 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 617 tokens (~308/item across 2 items; 2 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- Stability: pass → 0.97 functional
- 25 Oct 26 +1
- Stability: 0.97 → pass security
- 24 Oct 26 −6
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Stability: pass → 0.97 functional
- 18 Oct 26 +1
- Stability: 0.97 → pass security
- 16 Oct 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.
- 14 Oct 26 +43
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.87 ▲ functional
- Package version: 0.1.1 → 0.1.2 functional
- 13 Oct 26 0
- Package version: 0.1.1 → 0.1.2 functional
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/@three-ws/kol-mcp@0.1.2
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
get_wallet_portfolio KOL wallet portfolio + P&L ~250
Pull one KOL trader's live portfolio card from three.ws. Returns current holdings (total USD value, position count, and the single highest-value token the wallet holds) from the Birdeye proxy, plus realized P&L, win rate, trade count and volume over the last 30 days FIFO-computed from that wallet's own on-chain trades. Use this to size up a specific smart trader before copying or analyzing them. For ranking many traders at once use intel-mcp `kol_leaderboard`; this is the per-wallet deep dive. A null P&L field (with `pnl_source: null`) means three.ws has no trade history for that wallet in the window, which is an honest "unknown", NOT a flat or losing record: never report it as zero profit. `has_activity:false` means no holdings and no trades. If the holdings provider is down or rate-limited the call fails with `upstream_unavailable` rather than answering with an empty card, so an outage is never reported as a quiet wallet. Read-only live data.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | The Solana wallet address of the KOL trader to pull a portfolio card for. |
No output schema declared.
No examples provided.
get_wallet_trades A KOL wallet's trades on a mint ~186
Get one specific KOL trader's recent buys/sells of a given mint. The three.ws trade feed is scanned for that mint across all tracked wallets and narrowed to the wallet you pass, so you see exactly how that trader is positioning in that token — side (buy/sell), SOL size, token amount, per-trade price, USD value, and timestamp, newest first. Use it to inspect a single smart trader's moves before copying. For every tracked wallet's trades on a mint (not just one), use intel-mcp `kol_trades`. Read-only live data.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max number of this wallet's trades to return (1–100, default 20). |
| mint | string | yes | The token mint address to scan that wallet's activity on. |
| wallet | string | yes | The KOL wallet address whose trades to return. |
No output schema declared.
No examples provided.
How do I install the three.ws KOL MCP server?
three.ws KOL runs locally as an npm package, launched with npx -y @three-ws/kol-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 · @three-ws/kol-mcp
claude mcp add nirholas-kol-mcp -- npx -y @three-ws/kol-mcp
What is the three.ws KOL MCP server?
three.ws KOL is an MCP server listed in the public MCP registry as io.github.nirholas/kol-mcp. Per-wallet KOL deep dive, a tracked trader's portfolio P&L and its trades on a given mint. This page covers its npm package (@three-ws/kol-mcp).
Is the three.ws KOL MCP server safe to use?
three.ws KOL scores 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 three.ws KOL MCP server expose?
three.ws KOL exposes 2 tools: get_wallet_portfolio, get_wallet_trades. Their descriptions and schemas cost roughly 436 tokens of context every time the server is loaded.
Is the three.ws KOL MCP server still maintained?
three.ws KOL 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 three.ws KOL MCP server under?
three.ws KOL declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.