About three.ws Intel
three.ws Intel is an MCP server for AI agents that exposes read-only on-chain market intelligence from the public three.ws API, without requiring an API key.
Key features
- 01Score coins by smart-money activity
- 02Check wallet reputation and linkage
- 03Review signal-feed accuracy
- 04Rank KOL traders and inspect trades
- 05Browse copy-trade wallet listings
Use cases
- 01See which wallets are net-buying a coin
- 02Check wallet performance and shared-control evidence
- 03Compare signal accuracy and KOL P&L
- 04Find copy-trade wallets by chain or category
MCP support
The MCP server exposes seven read-only tools over stdio for querying live scores, feeds, and rankings from three.ws.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @three-ws/intel-mcpTHREE_WS_BASEBase URL of the three.ws API that serves the intel endpoints. Override only when self-hosting or targeting a preview deployment.THREE_WS_TIMEOUT_MSPer-request timeout in milliseconds for the live intel reads.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
6Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| mint | string | Yes | The token mint address to assess (any runtime mint). |
| network | enum | No | Solana network the mint lives on (default mainnet).mainnet | devnet |
Details
From the project README@three-ws/intel-mcp
Read the market the way the smart money does — smart-money scoring, wallet intel, signal feeds, KOL trades, and the copy-trade directory, from any AI agent.
A Model Context Protocol server that gives any AI assistant the three.ws market-intelligence surface over stdio. Judge a coin by who is buying it, pull a wallet's realized reputation, read a signal feed's proven accuracy, rank KOL traders, and browse the copy-trade Smart Money directory — all live, read-only, no key required.
Every score, signal, and ranking comes straight from the public three.ws API. No API key, no signer, no payment — point THREE_WS_BASE at a deployment and go.
Install
npm install @three-ws/intel-mcp
Or run with npx (no install):
npx @three-ws/intel-mcp
Quick start
Claude Code, one line:
claude mcp add intel -- npx -y @three-ws/intel-mcp
Claude Desktop / Cursor (claude_desktop_config.json or mcp.json):
{
"mcpServers": {
"intel": {
"command": "npx",
"args": ["-y", "@three-ws/intel-mcp"]
}
}
}
Inspect the surface with the MCP Inspector:
npx -y @modelcontextprotocol/inspector npx @three-ws/intel-mcp
Tools
| Tool | Type | What it does |
|---|---|---|
smart_money_coin | read-only | Score a coin by WHO is net-buying it — 0–100 smart-money score, reputable buyers, funder clusters, sybil flag. |
wallet_intel | read-only | One wallet's realized reputation: score, win rate, behavioral labels, and its funder cluster. |
wallet_linkage | read-only | Cross-check 2-10 Solana wallets for shared control: 0-100 same-controller score per pair, with evidence. |
signal_feed | read-only | A signal feed's proven accuracy (hit-rate, realized/follower ROI) and recent emissions with on-chain proof. |
kol_leaderboard | read-only | Rank tracked KOL traders by realized P&L over a 7d / 30d window. |
kol_trades | read-only | Recent KOL trades on a specific mint, across the tracked KOL set. |
copy_smart_wallets | read-only | Browse the ranked copy-trade Smart Money directory — filter by chain, category, and sort. |
All seven tools read live data: scores, feeds, and rankings move between calls, so none are idempotent.
Input parameters
smart_money_coin — mint (required), network (mainnet | devnet, default mainnet).
wallet_intel — wallet (required), network (mainnet | devnet, default mainnet).
wallet_linkage: addresses (required, array of 2-10 Solana addresses).
signal_feed — slug (required), network (mainnet | devnet, default mainnet).
kol_leaderboard — window (7d | 30d, default 7d), limit (1–100, default 25).
kol_trades — mint (required), limit (1–100, default 20).
copy_smart_wallets — chain (sol | bsc), category (smart_money | launchpad | kol | sniper), sort (profit | pnl | winrate | followers | score, default score), q (text), limit (1–100, default 30), offset (default 0).
Example
// copy_smart_wallets
> { "chain": "sol", "sort": "winrate", "limit": 3 }
{
"ok": true,
"count": 3,
"total": 412,
"offset": 0,
"limit": 3,
"has_more": true,
"facets": { "byChain": { "sol": 300, "bsc": 112 }, "byCategory": { "smart_money": 180, "kol": 90 } },
"wallets": [
{ "address": "…", "chain": "sol", "categories": ["smart_money"], "score": 94, "win_rate_30d": 0.71, "realized_profit_30d_usd": 182000, "follow_count": 1240 }
]
}
// smart_money_coin
> { "mint": "FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump" }
{
"ok": true,
"mint": "FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump",
"network": "mainnet",
"computed": true,
"smart_money_score": 78,
"reputable_buyers": 12,
"sybil_flag": false,
"sybil_share": 0.18,
"wallets": [ /* reputable buyers with realized_score, win_rate, labels */ ],
"clusters": [ /* funder clusters in the book */ ]
}
computed: false on a coin or wallet means the smart-money graph has no on-chain history for it yet — that's an honest "not enough data", not a failure.
// wallet_linkage
> { "addresses": ["FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump", "11111111111111111111111111111111"] }
{
"ok": true,
"addresses": ["FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump", "11111111111111111111111111111111"],
"pairs": [
{
"a": "FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump",
"b": "11111111111111111111111111111111",
"score": 0,
"band": "none",
"topSignal": null,
"signals": [],
"evidence": []
}
],
"complete": true
}
complete: false on the response means at least one address's history walk hit its time or request budget before finishing: scores are still real signals, just possibly based on partial history.
Requirements
- Node.js >= 20.
- Network access to
https://three.ws(or your ownTHREE_WS_BASE).
Environment variables
| Variable | Required | Default |
|---|---|---|
THREE_WS_BASE | no | https://three.ws |
THREE_WS_TIMEOUT_MS | no | 20000 |
Links
- Homepage: https://three.ws
- Changelog: https://three.ws/changelog
- Issues: https://github.com/nirholas/three.ws/issues
- License: Apache-2.0, see LICENSE
Part of the three.ws SDK suite — 3D AI agents, on-chain identity, and agent payments.
Website · Changelog · GitHub
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.