Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.aaronmsoto/tokenomics-overview-mcp

NPM · TOKENOMICS-OVERVIEW-MCP

Unofficial MCP server for AI tokenomics: Big-T notation, cache metrics, levers, FOCUS 1.5 AI.

+7 this week 87 Trust /100

Last scanned (2 hours ago)

Scores higher than 91% of npm servers

Category AI and Machine Learning

Trust breakdown (7 categories)

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
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to aaronmsoto/finops-framework-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 15 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 3489 tokens (~33/item across 103 items; 20 tools + 83 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 25% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 22 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
Changelog

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.

  • 4 Nov 26 +1

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

  • 3 Nov 26 +6
    • Stability: unverified → 0.47 ▲ functional
  • 21 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 20 Oct 26 65

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Analysed npm/tokenomics-overview-mcp@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo aaronmsoto/finops-framework-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/aaronmsoto/finops-framework-mcp/.github/workflows/publish.yml@refs/tags/v0.2.1
Rekor log index 3339854285
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:6220b6feb12a610117341e965b98ba6754588f3ef2e0968db31dacb5585e072b2f45abd688eda1d9463d2d60de3906d129b9563dbf1a9ff8cc4f95323

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 20 exposed · ~1,791 tokens

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 →

Tool Tokens
calculate_cache_metrics ~253

Applies the cache explainer's published formulas to YOUR token counts. Cache hit rate = cache read / (cache read + cache write + uncached input). Cache cost efficiency = 1 − actual prompt cost / uncached equivalent cost, where uncached equivalent cost = (cache read + cache write + uncached input) × base input price. Give token counts; add `base_input_price_per_mtok` plus either `actual_prompt_cost` or the read/write multipliers (e.g. 0.1 and 1.25) to also get cost efficiency. Compare per workload, not blended.

NameTypeReqDescription
actual_prompt_costnumber–Actual billed prompt (input-side) cost, if known
base_input_price_per_mtoknumber–Base (uncached) input price per million tokens
cache_read_multipliernumber–Cache read price as a multiple of base input, e.g. 0.1
cache_read_tokensnumberyes–
cache_write_multipliernumber–Cache write price as a multiple of base input, e.g. 1.25
cache_write_tokensnumberyes–
uncached_input_tokensnumberyes–
NameTypeReqDescription
actual_prompt_costnumber|nullyes–
actual_prompt_cost_sourcestringyes–
cache_cost_efficiencynumber|nullyes–
cache_hit_ratenumberyes–
cache_write_to_read_rationumber|nullyes–
formulasarrayyes–
interpretationstringyes–
total_input_tokensnumberyes–
uncached_equivalent_costnumber|nullyes–

No examples provided.

define_term ~60

Glossary lookup across the Foundation's definition page and the cache explainer (e.g. 'KV cache', 'prompt cache', 'tokenmaxing', 'Jevons paradox'). Returns every matching definition with its source.

NameTypeReqDescription
termstringyes–
NameTypeReqDescription
curriculum_matchesarrayyes–
matchesarrayyes–

No examples provided.

get_bigt_class ~102

One rung of the Big-T ladder: what puts a workload in it, the published fix, the stack layers whose levers move it, and the levers tagged with it. `class` accepts 'T(n·k)', 'n*k', 'nk', 'multiplicative', or a slug like 't-n-k'.

NameTypeReqDescription
classstringyese.g. 'T(n·k·a)' or 'agent-multiplicative'
NameTypeReqDescription
classobjectyes–
leversarrayyes–
moved_by_layersarrayyes–

No examples provided.

get_bigt_notation ~77

Big-T notation, 'Big-O for AI consumption': T(n · k · a) = requests × model calls per request × agent depth, and the six-class complexity ladder from T(1) to T(∞), each with its published fix. Use it to classify how a workload's token cost grows before optimizing constants.

Input schema present but exposes no named parameters.

NameTypeReqDescription
classesarrayyes–
expansionstringyes–
notationstringyes–
statusstringyes–
variablesarrayyes–

No examples provided.

get_crosslinks ~126

Stated links from tokenomics entities to the other two servers: each carries a quote from the Foundation page that names the target, and a finops://framework/… or focus://spec/… URI to read with those servers (null for FOCUS working-draft identifiers). Filter by `entity_type` + `slug` (e.g. metric cache-hit-rate) or by target `server`.

NameTypeReqDescription
cursorstring––
entity_typestring––
limitinteger––
serverstring––
slugstring––
NameTypeReqDescription
linksarrayyes–
nextCursorstring––
totalnumberyes–

No examples provided.

get_document ~96

Canonical markdown of one Tokenomics Foundation document, prefixed with its publication status and followed by CC BY attribution. Pass `section` (an id from list_documents) to get one section instead of the whole document — prefer this for long papers and podcast transcripts.

NameTypeReqDescription
documentstringyesDocument slug, e.g. 'cache-explainer'
sectionstring–Section id, e.g. 'tcmonitoring'
NameTypeReqDescription
documentobjectyes–
section–yes–

No examples provided.

get_focus_ai_tracker ~152

The Foundation's page on what FOCUS 1.5 does for AI cost, one card per capability: in the working draft (e.g. ModelId and other model properties on SKU Price Details, TokenCacheAction / TokenDirection, PrincipalId / CredentialId), in final Member review (SKU Price dataset, AI billing worked examples), and not in 1.5. Filter by `bucket` (done|review|out) or an `identifier` such as 'TokenCacheAction'. Nothing here is in a ratified FOCUS release until 1.5 is ratified; the FOCUS server serves ratified versions.

NameTypeReqDescription
bucketstring––
identifierstring––
NameTypeReqDescription
itemsarrayyes–
statusstringyes–

No examples provided.

get_layer ~99

One layer of the Seven-Layer Stack: description, components, published tooling table, and the levers that sit at it. `layer` accepts 'l5', '5', 'L5', the layer name ('ai access and control'), or its first word ('energy', 'demand'). L5 is the proxy / router / gateway layer.

NameTypeReqDescription
layerstringyese.g. 'l3' or 'inference stack'
NameTypeReqDescription
layerobjectyes–
leversarrayyes–

No examples provided.

get_lever ~39

Full record for one optimization lever, with provenance and status. Look up by slug or name from list_levers.

NameTypeReqDescription
leverstringyes–
NameTypeReqDescription
leverobjectyes–
uristringyes–

No examples provided.

get_metric ~61

One metric's published formula, definition, inputs, 'what good looks like' targets, and its cross-links to the FinOps Framework / FOCUS servers. E.g. 'cache-hit-rate', 'cache-cost-efficiency'.

NameTypeReqDescription
metricstringyes–
NameTypeReqDescription
crosslinksarrayyes–
crosswalkarrayyes–
metricobjectyes–
uristringyes–

No examples provided.

get_persona ~37

One persona's responsibilities, key decisions, signals and metrics, and stated links to FinOps Framework capabilities.

NameTypeReqDescription
personastringyes–
NameTypeReqDescription
crosslinksarrayyes–
crosswalkarrayyes–
personaobjectyes–
uristringyes–

No examples provided.

get_provider_cache_snapshot ~77

The cache explainer's dated snapshot of frontier providers' prompt-cache pricing and behavior (write/read charges as multiples of base input, minimum cacheable prefix, lifetime). A snapshot, not a spec — verify against current provider docs. Optional `provider` filter (anthropic, openai, google).

NameTypeReqDescription
providerstring––
NameTypeReqDescription
providersarrayyes–

No examples provided.

get_tokenomics_info ~39

Start here. Data version, entity counts, and every source document with its publication status (Working Draft, Release Candidate, …). No parameters.

Input schema present but exposes no named parameters.

NameTypeReqDescription
countsobjectyes–
crawled_atstringyes–
curriculum_loadedbooleanyes–
data_versionstringyes–
documentsarrayyes–
experimentalbooleanyes–
start_herearrayyes–

No examples provided.

list_documents ~51

Every ingested tokeneconomics.com document with kind (docs/project/paper/insight), publication status, and section ids for get_document. Optional `kind` filter.

NameTypeReqDescription
kindstring––
NameTypeReqDescription
documentsarrayyes–

No examples provided.

list_layers ~85

The seven layers (L0 Energy … L5 AI access and control, the routing/gateway layer … L6 Demand and entry points) with the published summary: whether each moves the Big-T multiplier, its key metric, and its primary levers. The lower three set what a token costs; the middle three move a workload between Big-T classes; the top layer sets demand.

Input schema present but exposes no named parameters.

NameTypeReqDescription
layersarrayyes–
statusstringyes–

No examples provided.

list_levers ~154

Optimization levers as the Foundation publishes them: the stack's primary levers per layer (caching, batching, right-sizing, quantization, complexity routing, budgets, agent caps…), Big-T's five levers (routing, serialization, caching, abstraction transparency, governance), architectural approaches with published token reductions, and the 34× worked-example steps. Filter by `layer` (0-6), `bigt_class`, `kind`, or `document`.

NameTypeReqDescription
bigt_classstring–e.g. 'T(n·k)'
cursorstring––
documentstring––
kindstring––
layerinteger––
limitinteger––
NameTypeReqDescription
leversarrayyes–
nextCursorstring––
totalnumberyes–

No examples provided.

list_metrics ~65

The Foundation's reference metrics with their published formulas: Cache Hit Rate, Cache Cost Efficiency and uncached equivalent cost (cache explainer), net benefit and risk expected loss (value classification), cost per token (definition), and AI unit economics (TCA over realized value, a proposal).

Input schema present but exposes no named parameters.

NameTypeReqDescription
metricsarrayyes–

No examples provided.

list_personas ~75

The eight core personas (Engineering, FinOps Practitioner, AI End User, Finance, Product, Procurement, Leadership, Capacity) and four allied ones, with the stages (Production, Consumption, Value) each spans. Filter by `stage` or `core`.

NameTypeReqDescription
coreboolean––
stagestring––
NameTypeReqDescription
personasarrayyes–
stagesarrayyes–

No examples provided.

list_value_categories ~58

The ten outcome categories (direct dollar wins, labor, intangible) with 'estimate as' units, and the five destinations Finance books realized value to. From 'Classifying and Measuring Realized Value from AI'.

NameTypeReqDescription
groupstring––
NameTypeReqDescription
booking_destinationsarrayyes–
categoriesarrayyes–
statusstringyes–

No examples provided.

search_tokenomics ~85

Ranked keyword search across layers, Big-T classes, levers, metrics, personas, value categories, glossary terms, FOCUS tracker items, and every document section. Use when you don't know the slug; follow up with the matching get_* tool or get_document(section).

NameTypeReqDescription
entity_typesarray––
limitinteger––
querystringyes–
NameTypeReqDescription
resultsarrayyes–

No examples provided.

Install

How do I install the io.github.aaronmsoto/tokenomics-overview-mcp server?

io.github.aaronmsoto/tokenomics-overview-mcp runs locally as an npm package, launched with npx -y tokenomics-overview-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 · tokenomics-overview-mcp

# add to Claude Code
claude mcp add aaronmsoto-tokenomics-overview-mcp -- npx -y tokenomics-overview-mcp
Common questions

What is the io.github.aaronmsoto/tokenomics-overview-mcp server?

io.github.aaronmsoto/tokenomics-overview-mcp is listed in the public MCP registry as io.github.aaronmsoto/tokenomics-overview-mcp. Unofficial MCP server for AI tokenomics: Big-T notation, cache metrics, levers, FOCUS 1.5 AI. This page covers its npm package (tokenomics-overview-mcp).

Is the io.github.aaronmsoto/tokenomics-overview-mcp server safe to use?

io.github.aaronmsoto/tokenomics-overview-mcp scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.aaronmsoto/tokenomics-overview-mcp server expose?

io.github.aaronmsoto/tokenomics-overview-mcp exposes 20 tools: get_tokenomics_info, list_documents, get_document, list_layers, get_layer, and 15 more. Their descriptions and schemas cost roughly 1,791 tokens of context every time the server is loaded.

Is the io.github.aaronmsoto/tokenomics-overview-mcp server still maintained?

io.github.aaronmsoto/tokenomics-overview-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 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 io.github.aaronmsoto/tokenomics-overview-mcp server under?

io.github.aaronmsoto/tokenomics-overview-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.