← Registry

Analytics

tokeneconomics.io

Provides tokenomics data, industry benchmarks, health scores, and peer comparisons for crypto projects.

1 endpoint28 known toolsFirst detected July 29, 2026Last detected July 29, 2026

ENDPOINT 1

https://tokeneconomics.io/api/mcp

No auth detected

MCP server metadata

Name
tokenomics-layer
Version
0.5.0
Capabilities
tools.listChangedresources.listChanged

Known tools 28

list_real_projects

List the real public tokenomics encoded in the dataset.

Inferred read-only
get_project_tokenomics

Get the full encoded tokenomics for one real project.

Inferred read-only
get_industry_benchmarks

Returns industry-median tokenomics benchmarks (team %, investor %, treasury %, TGE circulating %, etc.) derived from a curated set of blue-chip, source-verified launches (Uniswap, Arbitrum, Ethena, Jito, GMX, Pendle, Morpho) — see the result _note for the exact set + source URLs.

Inferred read-only
compute_health_score

Compute a 0-100 health score for a tokenomics design.

Inferred read-only
compare_to_peers

For a given design, return per-metric comparisons vs the 300+ real-world examples in the dataset.

Inferred read-only
compute_sell_pressure

Project monthly token unlocks + dollar-equivalent sell pressure for a design over the next N months.

Inferred read-only
compute_tge_circulating

Compute the % and absolute number of tokens circulating at TGE (token generation event / token launch).

Inferred read-only
propose_design_from_brief

Propose a starting tokenomics design from a one-paragraph project brief.

Inferred read-only
simulate_scenario

Simulate a what-if scenario for monthly token unlocks.

Inferred read-only
find_similar_projects

For a given design, find the closest matching projects in the 300+ protocol dataset by overall shape.

Inferred read-only
audit_design

Comprehensive risk audit of a tokenomics design.

Inferred read-only
validate_design

Validate that a tokenomics design is internally consistent: allocations sum to ~100%, vesting schedules are sane, no duplicate IDs, etc.

Inferred read-only
compute_dilution

For a design, return each allocation's share of CIRCULATING supply (the float) at checkpoints — by default TGE / 12 / 24 / 36 / 60 months.

Inferred read-only
simulate_price_bands

Run a Monte Carlo price-path simulation for a design.

Inferred read-only
analyze_sensitivity

Tornado analysis: rank the demand-side assumptions (staking sink, burn rate, demand growth, volatility) by how much each moves the median price at the horizon.

Inferred read-only
get_unlock_schedule

Month-by-month unlock schedule for a design: circulating supply as % of total each month, plus the absolute tokens unlocked that month.

Inferred read-only
model_demand

Translate a token-utility configuration (staking yield, fee burn, buyback, gas / governance / holder-rewards) into the demand-side assumptions (staking sink rate + annual burn rate) the price simulator uses, with a rationale for each.

Inferred read-only
project_holder_concentration

Project how concentrated the float is among allocations at future months (TGE / 6 / 12 / 24 by default).

Inferred read-only
diff_designs

Compare two candidate designs head-to-head.

Inferred read-only
search_by_metrics

Search the 300+ real launches by COMPUTED metric ranges — not just category/chain.

Inferred read-only
explain_term

Look up a tokenomics term in the glossary (TGE, FDV, cliff, vesting, HHI, float, etc.).

Inferred read-only
list_categories

List the valid filter values present in the dataset: the distinct categories, chains, and token types across the 300+ projects, each with a count.

Inferred read-only
generate_narrative

AI-GENERATED (spends model tokens): write launch narrative for a design — a tagline, an investor story, and a community story, grounded in the actual numbers.

Potential side effects
adversarial_review

AI-GENERATED (spends model tokens): pressure-test a design as three skeptics — a hostile VC, a crypto-Twitter skeptic, and a CEX listing committee.

Inferred read-only
get_upcoming_unlocks

Market intelligence: across the 300+ real projects, surface those with significant token unlocks coming up.

Inferred read-only
commit_design

Create a verifiable commitment of a tokenomics design so it can be proved and audited later.

Potential side effects
verify_design

Verify a tokenomics design against a commitment hash produced by commit_design.

Inferred read-only
export_disclosure

Generate a disclosure-ready export of a tokenomics design, structured to the four areas of the Token Transparency Framework (project/team, supply & allocation, vesting, financial/market).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.tokenomics-layer]
url = "https://tokeneconomics.io/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "tokenomics-layer": {
      "type": "http",
      "url": "https://tokeneconomics.io/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: tokenomics-layer
Remote MCP URL: https://tokeneconomics.io/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "tokenomics-layer": {
      "url": "https://tokeneconomics.io/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "tokenomics-layer": {
      "type": "http",
      "url": "https://tokeneconomics.io/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "tokenomics-layer",
  "transport": "streamable-http",
  "url": "https://tokeneconomics.io/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.