# Token Command Center (remote · token-command-center-gamma.vercel.app)

Free token data: revenue, net flow after emissions, supply/unlock history, catalysts, errors marked

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-07

## Components

- remote · `token-command-center-gamma.vercel.app`: 71/100 (this document), [markdown](https://verifymcp.io/servers/ysgjay-token-command-center/token-command-center-gamma.md), [page](https://verifymcp.io/servers/ysgjay-token-command-center/token-command-center-gamma)

## Channel facts

- Endpoint: `https://token-command-center-gamma.vercel.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-10-07.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1547 tokens (~96/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 74/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 23% 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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Token Command Center MCP server?

Token Command Center is a hosted endpoint at https://token-command-center-gamma.vercel.app/mcp, so there is nothing to install locally. 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 --transport http ysgjay-token-command-center 'https://token-command-center-gamma.vercel.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ysgjay-token-command-center": {
      "url": "https://token-command-center-gamma.vercel.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ysgjay-token-command-center": {
      "type": "http",
      "url": "https://token-command-center-gamma.vercel.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ysgjay-token-command-center]
url = "https://token-command-center-gamma.vercel.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ysgjay-token-command-center": {
      "type": "remote",
      "url": "https://token-command-center-gamma.vercel.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ysgjay-token-command-center --url 'https://token-command-center-gamma.vercel.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ysgjay-token-command-center:
    url: "https://token-command-center-gamma.vercel.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ysgjay-token-command-center": {
      "Transport": "http",
      "Url": "https://token-command-center-gamma.vercel.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ysgjay-token-command-center -t streamable-http -u 'https://token-command-center-gamma.vercel.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ysgjay-token-command-center": {
      "type": "http",
      "url": "https://token-command-center-gamma.vercel.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-10-07 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-06 (score 70, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-04 (score 69)

First indexed and scored.

## MCP tools (16)

### `tc_status` (~29 tokens)

Freshness, size and source-agreement stats of the token universe. Call first; quote generated_at.

### `tc_list_tokens` (~110 tokens)

Page through scored tokens with optional filters. Sorts: health, mcap, revenue, net_flow, ps, unlock_30d, alerts, name.

Input parameters:

- `category` (string)
- `descending` (boolean)
- `limit` (integer)
- `offset` (integer)
- `query` (string): Substring of slug, symbol or name.
- `sort` (string)
- `tier` (string)
- `verdict` (string): Real, Mid or Theater.

### `tc_get_token` (~107 tokens)

One token's full scorecard (about 8 KB): six pillar scores, the stat grid with a provenance tag per figure, ARR change over 1D/7D/30D/1Y, 30-point history, revenue basis, analyst facts, lens, links, gaps, and this token's alerts and source conflicts. Use only when tc_get_token_digest lacks what the user asked for.

Input parameters:

- `slug` (string, required): Token slug, e.g. geodnet.

### `tc_get_token_digest` (~80 tokens)

One token in about 1 KB: latest price, valuation, revenue and flows, 7- and 30-day changes, health score with its six pillar scores and verdict, supply unlocks, lens, and data-quality counts. Prefer this over tc_get_token.

Input parameters:

- `slug` (string, required): Token slug, e.g. geodnet.

### `tc_search_tokens` (~37 tokens)

Find slugs by symbol or name before calling tc_get_token_digest.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `tc_alerts` (~47 tokens)

Recent threshold alerts (revenue deterioration, emission acceleration, unlock cliffs, flow flips).

Input parameters:

- `limit` (integer)
- `severity` (string)
- `token` (string)

### `tc_categories` (~13 tokens)

Token counts per category.

### `tc_resolve` (~80 tokens)

Turn a symbol, $cashtag, name or slug into Token Command Center slugs. Returns exact (one slug) or ambiguous=true with every candidate when tokens share a symbol (e.g. POL); never guess between them. Call before a digest when the user names a token.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `tc_screen` (~399 tokens)

Screen the whole Book (all scored tokens) and get compact ranked rows. Filters: lens (long, short, no-edge), verdict (Real, Mid, Theater), tier, category, flow_model (comma-separated for several), stale, query; numeric ranges via min/max objects, e.g. {"min": {"health": 60, "arr": 1000000}, "max": {"ps": 20}}. Fields: alerts, arr (annualized revenue, USD), arr_30d (ARR change over 30 days, %), arr_7d (ARR change over 7 days, %), category, conflicts, date, fdv, flow_model, health (0-100 health score, set when the scorecard is written), health_change, holders_rev (annualized revenue to holders, USD), lens (long, short or no-edge), mcap, name, net_flow (holders revenue minus emissions, USD/yr), nf_yield (net flow / market cap, %), pct_unlocked, price, price_frozen_days, ps (market cap / annualized revenue), scorecard_age_days, stale, symbol, tier, unlock_30d (% of supply unlocking in the next 30 days), verdict (value accrual: Real, Mid or Theater). Tokens with no value for a ranged field are excluded, never counted as zero.

Input parameters:

- `category` (string)
- `fields` (array)
- `flow_model` (string)
- `lens` (string)
- `limit` (integer)
- `max` (object): Upper bounds by numeric field.
- `min` (object): Lower bounds by numeric field.
- `order` (string)
- `query` (string): Substring of slug, symbol or name.
- `sort` (string)
- `stale` (boolean)
- `tier` (string)
- `verdict` (string)

### `tc_compare` (~87 tokens)

Two to six tokens side by side: price, valuation, revenue and its 7/30-day change, holders revenue, net-flow yield, P/S, unlocks, health with six pillar scores, verdict, lens, and any frozen-price or old-scorecard flags. Accepts slugs or unambiguous symbols.

Input parameters:

- `fields` (array)
- `tokens` (array, required)

### `tc_brief` (~56 tokens)

The whole Book in about 1.5 KB: freshness and caveats, verdict and lens mix, biggest 30-day revenue movers, highest health, latest high alerts, plus a plain-text version. Use for market-wide questions.

### `tc_get_report` (~43 tokens)

Newest markdown scorecard for a slug (clipped). Long; prefer tc_get_token unless the user asks for the write-up.

Input parameters:

- `slug` (string, required)

### `tc_series` (~213 tokens)

One token's history as chartable series from TCC's daily snapshots (since 2026-06-09). Each metric returns `summary` {first, last, change_pct, min, max} first — answer trend questions from it — then at most 60 points (weekly by default). Frozen price feeds are null, not flat. Metrics: price, mcap, fdv, ann_fees, ann_revenue, ann_holders_rev, net_flow_usd, ps_ratio, health_score, ann_emissions_usd, circ_supply, total_supply, pct_unlocked, daily_fees, daily_revenue, daily_holders_rev, price_llama (daily_* and price_llama are DefiLlama, years deep; the rest are TCC snapshots).

Input parameters:

- `interval` (string)
- `metrics` (array)
- `range` (string)
- `slug` (string, required): Token slug, e.g. geodnet. Use tc_resolve first for a symbol.

### `tc_calendar` (~75 tokens)

Upcoming dated catalysts (unlocks, emission steps, votes, launches) across the Book, soonest first, at most 20. Optional token slug and horizon in days (default 30, max 180). Text is analyst notes.

Input parameters:

- `days` (integer)
- `token` (string): Token slug to filter to.

### `tc_moves` (~74 tokens)

Biggest movers: kind=movers ranks 30-day revenue change against price change (divergence); kind=momentum ranks a 14-day composite of revenue, net-flow yield and health changes. Up to 8 up and 8 down. Rows marked base_effect started from almost zero.

Input parameters:

- `kind` (string)

### `tc_ledger` (~37 tokens)

Prediction ledger tallies: open and graded call counts, next grading date, calls by side. Counts only; individual calls are not published.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ysgjay-token-command-center/token-command-center-gamma#diagnostics

## Score history

- 2026-10-07: 71
- 2026-10-06: 70
- 2026-10-04: 69

## Common questions

### What is the Token Command Center MCP server?

Token Command Center is an MCP server listed in the public MCP registry as io.github.ysgjay/token-command-center. Free token data: revenue, net flow after emissions, supply/unlock history, catalysts, errors marked. This page covers its hosted endpoint (https://token-command-center-gamma.vercel.app/mcp).

### Is the Token Command Center MCP server safe to use?

Token Command Center scores 71 out of 100 on VerifyMCP. 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 Token Command Center MCP server expose?

Token Command Center exposes 16 tools: tc_status, tc_list_tokens, tc_get_token, tc_get_token_digest, tc_search_tokens, and 11 more. Their descriptions and schemas cost roughly 1,487 tokens of context every time the server is loaded.

### Does the Token Command Center MCP server require authentication?

No. We connected to Token Command Center without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Token Command Center MCP server still maintained?

Token Command Center is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://token-command-center-gamma.vercel.app/mcp
- Website: https://token-command-center-gamma.vercel.app/docs
- Changelog RSS feed: https://verifymcp.io/servers/ysgjay-token-command-center/token-command-center-gamma.xml
- Changelog JSON feed: https://verifymcp.io/servers/ysgjay-token-command-center/token-command-center-gamma.json
- HTML version of this page: https://verifymcp.io/servers/ysgjay-token-command-center/token-command-center-gamma