three.ws Portfolio
NPM · @THREE-WS/PORTFOLIO-MCP
An agent's trading state — portfolio value, PnL, live balances, trade feed, and signed transfers.
Available components
Last scanned (3 hours ago)
Scores higher than 58% 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 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
- 55 of 187 dependencies flagged as unhealthy (1 deprecated). 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 Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1549 tokens (~258/item across 6 items; 6 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 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.
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 −2
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. security
- 23 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 +1
- Stability: 0.97 → pass security
- 15 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.90 ▲ functional
- Package version: 0.1.1 → 0.1.2 functional
- 12 Oct 26 0
- Package version: 0.1.1 → 0.1.2 functional
- 11 Oct 26 −40
- Stability: 0.87 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- License: unverified → pass ▲ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Licence: Apache-2.0 functional
- 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/portfolio-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 6 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-3gc7-fjrx-p6mg | CVE-2025-3194 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | no |
| GHSA-528h-pc64-c93x | CVE-2026-71429 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-hqr4-qq8f-hg3x | CVE-2026-104182 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-mjw6-4jj6-33hc | CVE-2026-104183 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L | yes |
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| 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 187 packages
| Packages resolved | 187 |
|---|---|
| Deprecated | 1 |
| Stale | 54 |
| No linked repository | 1 |
| 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_portfolio_asset My position in one token (holdings + market + chart) ~255
Deep-dive on ONE asset across every agent wallet you own. Returns which wallets hold it, your `total_amount` and `total_usd`, the per-wallet `holdings`, the live `market` data (price, 24h/7d/30d change, market cap, volume, ATH) and a `chart` of price history over `days`. Use `id:"native"` for the chain’s base coin (SOL on solana, ETH on evm), otherwise the base58 SPL mint or the 0x contract address. Requires THREE_WS_SESSION. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Which chain the asset lives on. |
| chain_id | integer | – | Optional EVM chain id (8453 Base, 1 Ethereum, 42161 Arbitrum, …). Pins which chain the contract is priced on; defaults to the chain of the wallets holding it. Ignored on solana. |
| days | integer | – | Days of price history for the chart, 1–365 (default 30). |
| id | string | yes | "native" for the base coin (SOL/ETH), otherwise the base58 SPL mint or 0x ERC-20 contract. |
No output schema declared.
No examples provided.
get_portfolio_history My portfolio value over time ~124
Time series of your total portfolio USD value, oldest point first, for charting performance over time. Returns `points` as { t (ISO timestamp), usd } pairs, drawn from snapshots persisted by get_portfolio_summary(snapshot:true) or the website. An empty `points` array means no snapshots have been captured yet in the window — take one with get_portfolio_summary(snapshot:true) to start the series. Requires THREE_WS_SESSION. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How many days of history to return, 1–365 (default 90). |
No output schema declared.
No examples provided.
get_portfolio_summary My agents’ live portfolio (holdings + USD value) ~190
Live aggregated portfolio for the agent wallets YOU own (resolved from your three.ws session). Returns `total_usd` across all wallets and a per-wallet breakdown — each with agent_id, agent_name, chain (solana | evm), address, the resolved .sol name when present, the native balance (SOL/ETH amount + USD), the SPL/ERC-20 token holdings (amount + USD), and that wallet’s USD subtotal. A wallet that failed to price carries `ok:false` and an `error` instead of throwing the whole call. Note: this is the live VALUE snapshot — realized PnL lives in get_trades_feed. Set `snapshot:true` to persist a point for the history chart. Requires THREE_WS_SESSION. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| snapshot | boolean | – | When true, also persist this total as a portfolio snapshot (feeds get_portfolio_history). Default false. |
No output schema declared.
No examples provided.
get_trades_feed Public closed-trade PnL feed ~320
The public feed of notable CLOSED positions across all three.ws agents, newest exit first — the canonical source of realized PnL on the platform. Each item carries the coin (mint, symbol, name), the trader (agent_id, agent_name, copier_count), entry_sol / exit_sol / realized_pnl_sol / realized_pnl_pct / multiple, where realized_pnl_pct and multiple are the whole position's return across every sell leg while entry_sol and exit_sol describe the remaining cost basis and the closing leg only, hold_seconds, exit_reason, the buy/sell signatures, and oracle conviction context when the coin was scored. Filter by `mint` to see every closed trade on one coin (the time window is ignored when a mint is set). Paginate with `cursor` = the previous response's `next_cursor`. No auth required — read-only live data.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | ISO timestamp for pagination — pass the previous response's `next_cursor`. |
| limit | integer | – | Max items to return, 1–80 (default 40). |
| min_pnl_pct | number | – | Minimum realized profit %, to surface only meaningful wins (default 10). |
| mint | string | – | Filter to a single coin by base58 mint. When set, all closed trades on that coin are returned regardless of window. |
| network | string | – | Solana network (default mainnet). |
| window | string | – | Time window for closed exits (default 24h). Ignored when `mint` is set. |
No output schema declared.
No examples provided.
get_wallet_balances Live on-chain balances for a Solana wallet ~151
Read live, on-chain balances for any Solana pubkey directly from the RPC: the native SOL balance plus every non-zero SPL token position (classic SPL and Token-2022), each with mint, raw amount, ui_amount, decimals, and which token program owns it. This is the raw on-chain truth (no USD pricing) — use it to confirm the agent’s own signing wallet before a send_transfer, or to check any address. No session required. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Base58 Solana pubkey to read balances for. |
| include_tokens | boolean | – | Include SPL/Token-2022 positions (default true). Set false for just the SOL balance. |
No output schema declared.
No examples provided.
send_transfer Send SOL or an SPL token on Solana mainnet ~322
BROADCASTS A REAL, IRREVERSIBLE SOLANA MAINNET TRANSACTION that moves funds out of the agent’s own wallet. Sends native SOL (omit `mint`, or set mint:"native") or any SPL token (pass its base58 `mint` — supplied at call time, e.g. the $THREE mint or any token you hold). Signs locally with the per-call `secret` (base58) or SOLANA_SECRET_KEY on the server; for a token it auto-creates the recipient’s associated token account when missing. Returns the confirmed signature, the moved amount, and a Solscan link. EXECUTION ACTION — pass confirm:true to proceed. Native sends are capped by MAX_SOL_PER_TX; the recipient must be in RECIPIENT_ALLOWLIST when one is configured.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to send, in human units as a decimal string (e.g. "1.5" SOL or "100" tokens). |
| confirm | boolean | – | Must be true to execute this irreversible transfer (when REQUIRE_CONFIRM is on). |
| mint | string | – | SPL token mint (base58) to send. Omit or set "native" to send SOL. Runtime input — any mint you hold. |
| priorityMicroLamports | integer | – | Compute-unit price in micro-lamports (default 100000). |
| recipient | string | yes | Destination Solana pubkey (base58). |
| secret | string | – | Base58 secret of the sending wallet. Falls back to SOLANA_SECRET_KEY on the server. |
No output schema declared.
No examples provided.
How do I install the three.ws Portfolio MCP server?
three.ws Portfolio runs locally as an npm package, launched with npx -y @three-ws/portfolio-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/portfolio-mcp
claude mcp add nirholas-portfolio-mcp -- npx -y @three-ws/portfolio-mcp
What is the three.ws Portfolio MCP server?
three.ws Portfolio is an MCP server listed in the public MCP registry as io.github.nirholas/portfolio-mcp. An agent's trading state, portfolio value, PnL, live balances, trade feed, and signed transfers. This page covers its npm package (@three-ws/portfolio-mcp).
Is the three.ws Portfolio MCP server safe to use?
three.ws Portfolio scores 78 out of 100 on VerifyMCP. We recorded 6 known advisories 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 Portfolio MCP server expose?
three.ws Portfolio exposes 6 tools: get_portfolio_summary, get_portfolio_history, get_portfolio_asset, get_trades_feed, get_wallet_balances, send_transfer. Their descriptions and schemas cost roughly 1,362 tokens of context every time the server is loaded.
Is the three.ws Portfolio MCP server still maintained?
three.ws Portfolio 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 Portfolio MCP server under?
three.ws Portfolio 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.