million
NPM · MILLION-MCP · SCANNED SEP 20
Operate a self-hosted Solana whale tracker and copy-trading deck: positions, rules, token checks.
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1015 tokens (~72/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the million MCP server?
million runs locally as an npm package, launched with npx -y million-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 · million-mcp
claude mcp add kelows-million -- npx -y million-mcp
{
"mcpServers": {
"kelows-million": {
"command": "npx",
"args": [
"-y",
"million-mcp"
]
}
}
} {
"servers": {
"kelows-million": {
"command": "npx",
"args": [
"-y",
"million-mcp"
]
}
}
} codex mcp add kelows-million -- npx -y million-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kelows-million": {
"type": "local",
"command": [
"npx",
"-y",
"million-mcp"
],
"enabled": true
}
}
} openclaw mcp add kelows-million --command npx --arg -y --arg million-mcp
mcp_servers:
kelows-million:
command: "npx"
args: ["-y", "million-mcp"] {
"McpServers": {
"kelows-million": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"million-mcp"
]
}
}
} assistant mcp add kelows-million -t stdio -c npx -a -y million-mcp
{
"mcpServers": {
"kelows-million": {
"command": "npx",
"args": [
"-y",
"million-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.
- 14 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Sept 26 55
First indexed and scored.
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/million-mcp@1.0.0
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 →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
analyze_wallet Analyze a wallet ~66
Fetch a roster wallet's trading history and compute its metrics: realized PnL in SOL, win rate, hold times, per-token breakdown and flags (bot, distributor, fresh wallet). Spends Helius credits.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Solana wallet address (base58) |
No output schema declared.
No examples provided.
check_token Run token checks ~67
Run the deck's safety checks on a token: mint and freeze authority, liquidity, market cap, holder concentration, deployer history, Jupiter sell simulation, RugCheck. Returns PASS, WARN or FAIL with each check.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Solana token mint address (base58) |
No output schema declared.
No examples provided.
find_token_buyers Find a token's biggest buyers ~122
Size buyers of a token, with a quick analysis preview and flags (bot, fresh wallet, cluster) for the biggest. The way to find wallets worth following. Spends Helius credits.
| Name | Type | Req | Description |
|---|---|---|---|
| min_sol | number | – | Minimum SOL a buyer spent, default 1 |
| mint | string | yes | Solana token mint address (base58) |
| mode | string | – | recent: latest transactions; deep: sampled across the token's history. Default recent |
| pages | integer | – | History pages to scan in recent mode, default 3 |
No output schema declared.
No examples provided.
get_book Positions ~36
Open and closed positions (paper or live) with size, entry and exit prices, PnL and exit reason, plus book statistics.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_decisions Decision log ~91
What the deck decided for recent token events from followed wallets, newest first: signals, opened positions, shadow trades and skips, each with its reason. Kept for 3 days.
| Name | Type | Req | Description |
|---|---|---|---|
| include_routine | boolean | – | Include routine skips (small buys, relays, transfers). Default false. |
| limit | integer | – | Default 50 |
| mint | string | – | Only decisions about this token |
No output schema declared.
No examples provided.
get_flows Roster order flow ~51
Tokens the followed wallets are accumulating or distributing right now, counted per owner (clusters of wallets vote once), bots excluded, buys netted against sells.
| Name | Type | Req | Description |
|---|---|---|---|
| minutes | integer | – | Window, default 30 |
No output schema declared.
No examples provided.
get_roster_holdings What the roster holds ~42
Tokens the followed wallets still hold, ranked by distinct owners and SOL still in at cost, and where the roster realized profit on round trips it watched close.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_rules Trading rules ~41
The trading rules in force: which signals trade, minimum buy sizes, position sizing, exits (trailing stop, stop loss), exposure caps and risk halts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_status Deck status ~48
Is the deck running, paper or live, is the live feed receiving events, how many wallets are followed, and a summary of the book (open positions, realized PnL, risk halt).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_wallet Wallet details ~42
A roster wallet's stored analysis, live activity, subscription state and linked wallets of the same owner.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Solana wallet address (base58) |
No output schema declared.
No examples provided.
import_wallets Add wallets to the roster ~56
Add wallet addresses to the roster (not followed yet). Analyze them, then subscribe the ones the user picks.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Source tag, e.g. "found via CATE" |
| wallets | array | yes | – |
No output schema declared.
No examples provided.
set_wallet_subscription Follow or unfollow a wallet ~64
Follow (subscribe) or unfollow a roster wallet. Followed wallets feed the live feed and can trigger trades. Only do this when the user asked for that wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Solana wallet address (base58) |
| subscribed | boolean | yes | – |
No output schema declared.
No examples provided.
update_rules Change trading rules ~95
Change some trading rule fields (use get_rules for names and current values). Only the given fields change; the deck validates and may clamp values. Applies to new signals; open positions keep their exits. Cannot switch paper to live. Returns each changed field before and after.
| Name | Type | Req | Description |
|---|---|---|---|
| changes | object | yes | Field → new value, e.g. { "positionSol": 0.2, "tradeSignals": "consensus" } |
No output schema declared.
No examples provided.
why_not_bought Why it did or didn't buy a token ~66
Everything needed to explain why the deck did or did not buy one token: its decision history (routine skips included), the token's check report, any position in it, and the trading rules in force.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Solana token mint address (base58) |
No output schema declared.
No examples provided.
What is the million MCP server?
million is an MCP server listed in the public MCP registry as io.github.Kelows/million. Operate a self-hosted Solana whale tracker and copy-trading deck: positions, rules, token checks. This page covers its npm package (million-mcp).
Is the million MCP server safe to use?
million scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting 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 million MCP server expose?
million exposes 14 tools: get_status, get_book, get_decisions, why_not_bought, get_rules, and 9 more. Their descriptions and schemas cost roughly 887 tokens of context every time the server is loaded.
Is the million MCP server still maintained?
million 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.
What licence is the million MCP server under?
million declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.