# $THREE Token MCP server

Agent View of the PolicyLayer registry record for $THREE Token: identity, probed posture, risk grade, and all 3 tools classified. HTML page: https://policylayer.com/tools/io-github-nirholas-three-token-mcp

## Facts

- Server id: `@three-ws/three-token-mcp`
- Install: `npx -y @three-ws/three-token-mcp`
- Homepage: https://github.com/nirholas/three.ws
- Registry record: grade F, identity unverified
- Lifecycle: active
- Rate-limited: no
- Tools: 3 (3 with introspected schema)
- Tool categories present: Destructive, Read
- Context-window cost: 557 tokens per request — https://policylayer.com/token-cost/io-github-nirholas-three-token-mcp
- Tags: io github nirholas three token mcp, admin
- Record last modified: 2026-07-09T19:42:12.744Z

## Tools (3)

| Tool | Category | Risk | Record |
| --- | --- | --- | --- |
| `three_burn` | Destructive | Critical | https://policylayer.com/tools/io-github-nirholas-three-token-mcp/three-burn.md |
| `three_balance` | Read | Low | https://policylayer.com/tools/io-github-nirholas-three-token-mcp/three-balance.md |
| `three_price` | Read | Low | https://policylayer.com/tools/io-github-nirholas-three-token-mcp/three-price.md |

## Tool descriptions

- `three_burn` — 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. EX…
- `three_balance` — 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.
- `three_price` — 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.

## Related servers

- UnClick (1658 tools) — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server.md
- Nodebench (824 tools) — https://policylayer.com/tools/io-github-homenshum-nodebench.md
- Yaver (808 tools) — https://policylayer.com/tools/io-github-kivanccakmak-yaver.md
- Binance MCP Server (734 tools) — https://policylayer.com/tools/nirholas-binance-mcp.md
- Pfsense (680 tools) — https://policylayer.com/tools/abl030-pfsense-mcp.md
- AdButler (622 tools) — https://policylayer.com/tools/adbutler.md
- Fortimanager (584 tools) — https://policylayer.com/tools/jmpijll-fortimanager-mcp.md
- Crow (578 tools) — https://policylayer.com/tools/kh0pper-crow.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=io-github-nirholas-three-token-mcp · API: https://policylayer.com/registry/api · Recommended policies for every tool: https://policylayer.com/policies/io-github-nirholas-three-token-mcp