three.ws KOL runs on your own machine — the client starts it, so there is no endpoint to ping. 74 installs a week from npm. Last commit 1 Nov 2026.
Per-wallet KOL deep dive — a tracked trader's portfolio P&L and its trades on a given mint.
What the code does
We read the source, 22 h ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
'http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/token',
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
UPDATE destination_whitelist_settings
SET cooldown_seconds = ${ch.cooldown_seconds ?? row.cooldown_seconds},
const r = await redis.eval(
const proc = spawn(ffmpegPath(), ['-hide_banner', '-loglevel', 'error', '-i', 'pipe:0', ...args, 'pipe:1']);
const raw = JSON.parse(await readFile(path.join(ROOT, dir, 'server.json'), 'utf8'));
lambda: subprocess.run(
COPY --parents package.json package-lock.json .npmrc* **/package.json /app/
if (reset) { state.cursor = null; state.total = 0; grid.innerHTML = skeletons(); stateEl.hidden = true; }
`https://api.telegram.org/bot${cfg.token}/sendMessage`,
"bytecode": "0x60806040523480156200001157600080fd5b5060405162000dd238038062000dd2833981016040819052620000349162000351565b8383600362000044838262000477565b50600462000053828262000477565b5050506001600160a01b038116620000a65760405162461bcd60e51b8152602060048201526011602482015270726…
const entries = await readdir(path.join(ROOT, parent), { withFileTypes: true });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found things in this code
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch three.ws KOL and you get told the day something new turns up.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add kol-mcp -- npx -y @three-ws/kol-mcp{
"mcpServers": {
"kol-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/kol-mcp"
]
}
}
}[mcp_servers.kol-mcp]
command = "npx"
args = ["-y", "@three-ws/kol-mcp"]{
"mcpServers": {
"kol-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/kol-mcp"
]
}
}
}{
"servers": {
"kol-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@three-ws/kol-mcp"
]
}
}
}Optional settings from the registry entry, left out of the block above:
THREE_WS_BASE (Base URL of the three.ws API that serves the KOL endpoints. Override only when self-hosting or targeting a preview deployment), THREE_WS_TIMEOUT_MS (Per-request timeout in milliseconds for the live KOL reads).
Alternatives to three.ws KOL
same job, measured the same wayRead-only Polymarket sports and esports data: wallet grades on settled P&L, large trades, markets.
An agent's trading state — portfolio value, PnL, live balances, trade feed, and signed transfers.
Give your AI agent an x402 wallet: discover and pay for services in USDC, or earn from your own.
Coin smart-money scores, wallet reputation, signal feeds, and KOL leaderboards.
Live Polymarket data for agents: markets, insider-scored whale trades, leaderboards, wallet P&L
HeyAnon on-chain agent: wallets, portfolios, DeFi and CEX actions, transfers, Gemma research.
MCP server for Pear Protocol: markets, positions, orders, portfolio, and gated trade execution.
Source-backed county property records, owner-name portfolios and three Hamilton County lead packa...
three.ws KOL — questions
Answers built from our own checks of this server.