Token Command Center MCP server
io.github.ysgjay/token-command-centerysgjaystreamable-httpv0.3.0Scanned
Free token data: revenue, net flow after emissions, supply/unlock history, catalysts, errors marked
18 tools: 9 change things and 9 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
9 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Token Command Center MCP server can do
The Token Command Center MCP server is published by the GitHub account ysgjay. It has 18 tools. It can create or change data (9 tools: tc_alerts, tc_categories, tc_screen, tc_brief and 5 more), but cannot delete data. 9 tools only read.
1 tool reads private data (tc_get_token_digest).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 21, 2026, version 0.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
18 tools
Changes things 9Claude Code: ask
tc_alertsRecent threshold alerts (revenue deterioration, emission acceleration, unlock cliffs, flow flips).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Recent threshold alerts (revenue deterioration, emission acceleration, unlock cliffs, flow flips).
Annotations the server declares
- title: Alerts
- readOnlyHint: true
- openWorldHint: false
tc_briefThe 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Book brief
- readOnlyHint: true
- openWorldHint: false
tc_calendarUpcoming dated catalysts (unlocks, emission steps, votes, launches) across the Book, soonest first, at most 20.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Upcoming dated catalysts (unlocks, emission steps, votes, launches) across the Book, soonest first, at most 20. Optional token slug, tokens (several slugs), kind and horizon in days (default 30, max 180). Text is analyst notes; each event also has symbol, kind, estimated (date marked approximate), a plain title with title_source (curated: hand-written for this note; measured: from the measured unlock size; note: cut from the note), and the measured next unlock (pct_circ, pct_supply, tokens, source, as_of; CoinMarketCap) when it falls within a day of the event, else null. Events whose text starts 'Scheduled unlock' come from the measured schedule alone, fill only slots the analyst events leave free, and are counted in scheduled_total.
Annotations the server declares
- title: Catalyst calendar
- readOnlyHint: true
- openWorldHint: false
tc_categoriesToken counts per category.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Token counts per category.
Annotations the server declares
- title: Categories
- readOnlyHint: true
- openWorldHint: false
tc_ledgerPrediction ledger tallies: open and graded call counts, next grading date, calls by side.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Prediction ledger tallies: open and graded call counts, next grading date, calls by side. Counts only; individual calls are not published.
Annotations the server declares
- title: Ledger tallies
- readOnlyHint: true
- openWorldHint: false
tc_movesBiggest 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.1 finding
Why it is in this group
- The name "tc_moves" says "move": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "tc_moves" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "tc_moves" says "move": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Movers and momentum
- readOnlyHint: true
- openWorldHint: false
tc_projectsRevenue-earning projects with NO token (wallets, trading bots, apps, launchpads, stablecoin issuers, listed companies): yearly revenue on the 30-day pace, last 12 months, 30-day ch…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Revenue-earning projects with NO token (wallets, trading bots, apps, launchpads, stablecoin issuers, listed companies): yearly revenue on the 30-day pace, last 12 months, 30-day change, category, chains, token_status (none, points, announced, public_equity with a stock ticker, launched). Figures only, no health score. Use with tc_screen to rank apps and tokens together in a category. Source DefiLlama, with link and date; rows with flags need a caveat.
Annotations the server declares
- title: Projects without a token
- readOnlyHint: true
- openWorldHint: false
tc_screenScreen the whole Book (all scored tokens) and get compact ranked rows.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Screen the whole Book (all scored tokens) and get compact ranked rows. Filters: lens (long, short, no-edge), verdict (Real, Mid, Theater), tier, category, sector (a clean label such as Lending or Memes), 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, sector (one clean sector beside the raw category, or null), 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.
Annotations the server declares
- title: Screen the Book
- readOnlyHint: true
- openWorldHint: false
tc_seriesOne token's history as chartable series from TCC's daily snapshots (since 2026-06-09).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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).
Annotations the server declares
- title: Token history series
- readOnlyHint: true
- openWorldHint: false
Only reads 9Show 9 read-only tools
tc_compareTwo to six tokens side by side: price, valuation, revenue and its 7/30-day change, revenue_figures per token (30-day annualized pace and real last-12-months revenue, P/S on both), …No findings
Why it is in this group
- The name "tc_compare" says "compare": a word for reading.
Description, as the server wrote it Two to six tokens side by side: price, valuation, revenue and its 7/30-day change, revenue_figures per token (30-day annualized pace and real last-12-months revenue, P/S on both), 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.
Annotations the server declares
- title: Compare tokens
- readOnlyHint: true
- openWorldHint: false
tc_get_projectOne coinless project by slug (from tc_projects): revenue figures, products, chains, token_status, source link and date.No findings
Why it is in this group
- The name "tc_get_project" says "get": a word for reading.
Description, as the server wrote it One coinless project by slug (from tc_projects): revenue figures, products, chains, token_status, source link and date.
Annotations the server declares
- title: Project without a token
- readOnlyHint: true
- openWorldHint: false
tc_get_reportNewest markdown scorecard for a slug (clipped).No findings
Why it is in this group
- The name "tc_get_report" says "get": a word for reading.
Description, as the server wrote it Newest markdown scorecard for a slug (clipped). Long; prefer tc_get_token unless the user asks for the write-up.
Annotations the server declares
- title: Scorecard report
- readOnlyHint: true
- openWorldHint: false
tc_get_tokenOne 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 f…No findings
Why it is in this group
- The name "tc_get_token" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Token scorecard
- readOnlyHint: true
- openWorldHint: false
tc_get_token_digestOne token in about 2 KB: latest price, valuation, revenue and flows, 7- and 30-day changes, revenue_figures (the 30-day annualized pace AND the real last-12-months revenue, P/S on …Reads private dataNo findings
Why it is in this group
- The name "tc_get_token_digest" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "note": it reads notes.
Description, as the server wrote it One token in about 2 KB: latest price, valuation, revenue and flows, 7- and 30-day changes, revenue_figures (the 30-day annualized pace AND the real last-12-months revenue, P/S on both, one-line notes on how each is formed), health score with its six pillar scores and verdict, supply unlocks, lens, and data-quality counts. Prefer this over tc_get_token.
Annotations the server declares
- title: Token digest
- readOnlyHint: true
- openWorldHint: false
tc_list_tokensPage through scored tokens with optional filters.No findings
Why it is in this group
- The name "tc_list_tokens" says "list": a word for reading.
Description, as the server wrote it Page through scored tokens with optional filters. Sorts: health, mcap, revenue, net_flow, ps, unlock_30d, alerts, name.
Annotations the server declares
- title: List tokens
- readOnlyHint: true
- openWorldHint: false
tc_resolveTurn a symbol, $cashtag, name or slug into Token Command Center slugs.No findings
Why it is in this group
- The name "tc_resolve" says "resolve": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Resolve token
- readOnlyHint: true
- openWorldHint: false
tc_search_tokensFind slugs by symbol or name before calling tc_get_token_digest.No findings
Why it is in this group
- The name "tc_search_tokens" says "search": a word for reading.
Description, as the server wrote it Find slugs by symbol or name before calling tc_get_token_digest.
Annotations the server declares
- title: Search tokens
- readOnlyHint: true
- openWorldHint: false
tc_statusFreshness, size and source-agreement stats of the token universe.No findings
Why it is in this group
- The name "tc_status" says "status": a word for reading.
Description, as the server wrote it Freshness, size and source-agreement stats of the token universe. Call first; quote generated_at.
Annotations the server declares
- title: Universe status
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:13 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 9
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 9 tools that change things (9 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://token-command-center-gamma.vercel.app/mcp: tools/list returned 18 tools to an anonymous client, including tc_alerts (write), tc_categories (write), tc_screen (write), tc_brief (write), tc_series (write) and 4 more
Posture changes
- Nov 6, 2026
- Tools that change things, listed without credentials: 8 to 9
Findings
Matches of fixed checks, with the text they matched.
- Warntc_moves
The server marks "tc_moves" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "tc_moves" says "move": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:tc_calendarChanges thingsdescriptioninputSchema
- Changed:tc_compareOnly readsinputSchema
- Changed:tc_screenChanges thingsdescriptioninputSchema
Tools2 added.+2 addedView diff
- Added:tc_get_projectOnly reads
- Added:tc_projectsChanges things
PostureRemote posture changed. Tools that change things, listed without credentials: 8 -> 9.View diff
- Tools that change things, listed without credentials: 8 to 9
Install
Pinned to version 0.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http token-command-center https://token-command-center-gamma.vercel.app/mcpclaude mcp add --transport http token-command-center https://token-command-center-gamma.vercel.app/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__token-command-center__tc_status",
"mcp__token-command-center__tc_list_tokens",
"mcp__token-command-center__tc_get_token",
"mcp__token-command-center__tc_get_token_digest",
"mcp__token-command-center__tc_search_tokens",
"mcp__token-command-center__tc_resolve",
"mcp__token-command-center__tc_compare",
"mcp__token-command-center__tc_get_report",
"mcp__token-command-center__tc_get_project"
],
"ask": [
"mcp__token-command-center__tc_alerts",
"mcp__token-command-center__tc_categories",
"mcp__token-command-center__tc_screen",
"mcp__token-command-center__tc_brief",
"mcp__token-command-center__tc_series",
"mcp__token-command-center__tc_calendar",
"mcp__token-command-center__tc_moves",
"mcp__token-command-center__tc_ledger",
"mcp__token-command-center__tc_projects"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as token-command-center. Review it before you use it.
Capability tags behind 1 rule
- mcp__token-command-center__tc_get_token_digest private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ysgjay/token-command-center/verify?hash=15101879d7a2643ff964e13d6d1cb76775ee1a7578511af4851afba6bada3717" | jq -e '.changed == false'Pinned hash 15101879d7a2, from Nov 21, 2026, 06:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.ysgjay/token-command-center/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.ysgjay/token-command-center)Source: MCP Registry. Synced Oct 21, 2026, 18:52 UTC.
Token Command Center MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Token Command Center MCP server safe?
- No scan can promise that. What its definitions show: 18 tools, 9 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Token Command Center MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Token Command Center MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Token Command Center MCP server have?
- 18 tools: 9 write, 9 read. tc_alerts, tc_categories, tc_screen, tc_brief, tc_series, tc_calendar, tc_moves, tc_ledger and 10 more.
Does the Token Command Center MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Token Command Center MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Token Command Center MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.