# million (npm · million-mcp)

Operate a self-hosted Solana whale tracker and copy-trading deck: positions, rules, token checks.

- Trust score: 70/100 (medium)
- Change this week: +15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `million-mcp`: 70/100 (this document), [markdown](https://verifymcp.io/servers/kelows-million/million-mcp.md), [page](https://verifymcp.io/servers/kelows-million/million-mcp)

## Channel facts

- Registry: `npm`
- Package: `million-mcp`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1015 tokens (~72/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add kelows-million -- npx -y million-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "kelows-million": {
      "command": "npx",
      "args": [
        "-y",
        "million-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kelows-million": {
      "command": "npx",
      "args": [
        "-y",
        "million-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add kelows-million -- npx -y million-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kelows-million": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "million-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kelows-million --command npx --arg -y --arg million-mcp
```

### Hermes

```yaml
mcp_servers:
  kelows-million:
    command: "npx"
    args: ["-y", "million-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "kelows-million": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "million-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add kelows-million -t stdio -c npx -a -y million-mcp
```

### Other

```json
{
  "mcpServers": {
    "kelows-million": {
      "command": "npx",
      "args": [
        "-y",
        "million-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-14 (score 70, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-13 (score 55)

First indexed and scored.

## MCP tools (14)

### `get_status` (~48 tokens)

Deck status

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).

### `get_book` (~36 tokens)

Positions

Open and closed positions (paper or live) with size, entry and exit prices, PnL and exit reason, plus book statistics.

### `get_decisions` (~91 tokens)

Decision log

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.

Input parameters:

- `include_routine` (boolean): Include routine skips (small buys, relays, transfers). Default false.
- `limit` (integer): Default 50
- `mint` (string): Only decisions about this token

### `why_not_bought` (~66 tokens)

Why it did or didn't buy a token

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.

Input parameters:

- `mint` (string, required): Solana token mint address (base58)

### `get_rules` (~41 tokens)

Trading rules

The trading rules in force: which signals trade, minimum buy sizes, position sizing, exits (trailing stop, stop loss), exposure caps and risk halts.

### `update_rules` (~95 tokens)

Change trading rules

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.

Input parameters:

- `changes` (object, required): Field → new value, e.g. { "positionSol": 0.2, "tradeSignals": "consensus" }

### `get_flows` (~51 tokens)

Roster order flow

Tokens the followed wallets are accumulating or distributing right now, counted per owner (clusters of wallets vote once), bots excluded, buys netted against sells.

Input parameters:

- `minutes` (integer): Window, default 30

### `get_roster_holdings` (~42 tokens)

What the roster holds

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.

### `check_token` (~67 tokens)

Run token checks

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.

Input parameters:

- `mint` (string, required): Solana token mint address (base58)

### `find_token_buyers` (~122 tokens)

Find a token's biggest buyers

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.

Input parameters:

- `min_sol` (number): Minimum SOL a buyer spent, default 1
- `mint` (string, required): 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

### `import_wallets` (~56 tokens)

Add wallets to the roster

Add wallet addresses to the roster (not followed yet). Analyze them, then subscribe the ones the user picks.

Input parameters:

- `label` (string): Source tag, e.g. "found via CATE"
- `wallets` (array, required)

### `analyze_wallet` (~66 tokens)

Analyze a wallet

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.

Input parameters:

- `address` (string, required): Solana wallet address (base58)

### `get_wallet` (~42 tokens)

Wallet details

A roster wallet's stored analysis, live activity, subscription state and linked wallets of the same owner.

Input parameters:

- `address` (string, required): Solana wallet address (base58)

### `set_wallet_subscription` (~64 tokens)

Follow or unfollow a wallet

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.

Input parameters:

- `address` (string, required): Solana wallet address (base58)
- `subscribed` (boolean, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/kelows-million/million-mcp#diagnostics

## Score history

- 2026-09-20: 70
- 2026-09-19: 70
- 2026-09-18: 70
- 2026-09-17: 70
- 2026-09-16: 70
- 2026-09-15: 70
- 2026-09-14: 70
- 2026-09-13: 55

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/million-mcp
- Socket report: https://socket.dev/npm/package/million-mcp
- Repository: https://github.com/Kelows/million
- Changelog RSS feed: https://verifymcp.io/servers/kelows-million/million-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/kelows-million/million-mcp.json
- HTML version of this page: https://verifymcp.io/servers/kelows-million/million-mcp