$THREE Token
NPM · @THREE-WS/THREE-TOKEN-MCP · SCANNED SEP 20
Price, hold, and burn $THREE on Solana — the first MCP server whose actions burn a token.
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 Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects uuid 8.3.2, reached via @solana/web3.js > jayson > uuid. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 54 of 167 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency35
- 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
- License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 8 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 582 tokens (~194/item across 3 items; 3 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 Management83
- Stability observed for 25 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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 $THREE Token MCP server?
$THREE Token runs locally as an npm package, launched with npx -y @three-ws/three-token-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/three-token-mcp
claude mcp add nirholas-three-token-mcp -- npx -y @three-ws/three-token-mcp
{
"mcpServers": {
"nirholas-three-token-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/three-token-mcp"
]
}
}
} {
"servers": {
"nirholas-three-token-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/three-token-mcp"
]
}
}
} codex mcp add nirholas-three-token-mcp -- npx -y @three-ws/three-token-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nirholas-three-token-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@three-ws/three-token-mcp"
],
"enabled": true
}
}
} openclaw mcp add nirholas-three-token-mcp --command npx --arg -y --arg @three-ws/three-token-mcp
mcp_servers:
nirholas-three-token-mcp:
command: "npx"
args: ["-y", "@three-ws/three-token-mcp"] {
"McpServers": {
"nirholas-three-token-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@three-ws/three-token-mcp"
]
}
}
} assistant mcp add nirholas-three-token-mcp -t stdio -c npx -a -y @three-ws/three-token-mcp
{
"mcpServers": {
"nirholas-three-token-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/three-token-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.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 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.
- 14 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.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
- Security disclosure: unverified → pass ▲ functional
- 8 Sept 26 0
- Security disclosure: pass → unverified ▼ 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 20 Sept 2026 · Analysed npm/@three-ws/three-token-mcp@1.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 3 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-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 |
Background: What a vulnerability scan can and cannot prove →
Dependencies 167 packages
| Packages resolved | 167 |
|---|---|
| Deprecated | 2 |
| Stale | 52 |
| 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 →
three_balance Read a wallet's $THREE + SOL balance ~68
Return the $THREE and SOL balance for a Solana pubkey. If no pubkey is given, uses the configured signer (SOLANA_SECRET_KEY). Read-only — no payment.
| Name | Type | Req | Description |
|---|---|---|---|
| pubkey | string | – | Base58 pubkey to read. Defaults to the configured signer's address. |
No output schema declared.
No examples provided.
three_burn Burn $THREE on-chain (incinerator + treasury split) ~266
Burn a USD-denominated amount of the $THREE your wallet holds. Quotes USD→$THREE via Jupiter, then sends ONE Solana transaction that splits it between the incinerator (burn) and the three.ws treasury, per the live public token config. EXECUTION ACTION — signs and broadcasts on Solana mainnet, IRREVERSIBLE: pass confirm:true. Capped by MAX_BURN_USD. The resolved mint is asserted to be canonical $THREE before signing. Requires a signer (SOLANA_SECRET_KEY env or the `secret` arg) holding enough $THREE. Returns the tx signature, the burned/treasury breakdown, and a Solscan link.
| Name | Type | Req | Description |
|---|---|---|---|
| burnBps | number | – | Share routed to the incinerator in basis points. Default 5000 (50% burn / 50% treasury). 10000 = burn everything. |
| confirm | boolean | – | Must be true to execute this irreversible burn (when REQUIRE_CONFIRM is on). |
| memo | string | – | Optional note appended to the on-chain memo. |
| secret | string | – | Base58 signer override. Defaults to SOLANA_SECRET_KEY. Treat like cash. |
| usd | number | yes | USD value of $THREE to burn (priced live via Jupiter). |
No output schema declared.
No examples provided.
three_price Live $THREE price (Jupiter) + USD→$THREE quote ~74
Return the live USD price of $THREE (Jupiter primary, Birdeye fallback). Pass `usd` to also get how much $THREE that amount buys (token amount + atomic units). Read-only — no signer or payment required.
| Name | Type | Req | Description |
|---|---|---|---|
| usd | number | – | Optional USD amount to quote into $THREE. |
No output schema declared.
No examples provided.
What is the $THREE Token MCP server?
$THREE Token is an MCP server listed in the public MCP registry as io.github.nirholas/three-token-mcp. Price, hold, and burn $THREE on Solana, the first MCP server whose actions burn a token. This page covers its npm package (@three-ws/three-token-mcp).
Is the $THREE Token MCP server safe to use?
$THREE Token scores 76 out of 100 on VerifyMCP. We recorded 3 known advisories against it as of 20 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 $THREE Token MCP server expose?
$THREE Token exposes 3 tools: three_price, three_balance, three_burn. Their descriptions and schemas cost roughly 408 tokens of context every time the server is loaded.
Is the $THREE Token MCP server still maintained?
$THREE Token is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.