Defillama
NPM · @PIPEWORX/MCP-DEFILLAMA · 2 COMPONENTS
DefiLlama MCP — DeFi analytics from DefiLlama (free, no auth)
Available components
Last scanned (15 minutes ago)
Scores higher than 81% of npm servers
Category Crypto and Web3
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-defillama). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1180 tokens (~131/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 5 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 81
First indexed and scored.
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 6 Nov 2026 · Analysed npm/@pipeworx/mcp-defillama@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 | pipeworx-io/mcp-defillama |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-defillama/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3617496960 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a091ff65464c969d8dab95a9b8e6e4d28da0f61101f8b16dd1701579da82ddfc7ee92a683f81825e34994e501ee2adef8efe960f0e47b9bb966e70b2b |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
defi_chain_tvl ~31
Compare total value locked across all blockchains. Returns TVL per chain to identify where capital is concentrated.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
defi_protocol_detail ~61
Get detailed metrics for a specific DeFi protocol including TVL history over time, breakdown by blockchain, and token information.
| Name | Type | Req | Description |
|---|---|---|---|
| protocol | string | yes | Protocol slug (e.g., "aave", "uniswap", "lido", "makerdao") |
No output schema declared.
No examples provided.
defi_protocol_fees ~84
Check daily fees and revenue for a DeFi protocol. Returns fee trends to analyze profitability and income changes over time.
| Name | Type | Req | Description |
|---|---|---|---|
| data_type | string | – | Type of data: "dailyFees" or "dailyRevenue" (default: "dailyFees") |
| protocol | string | yes | Protocol slug (e.g., "aave", "uniswap", "lido") |
No output schema declared.
No examples provided.
defi_revenue_ranking ~295
Rank DeFi protocols by revenue (or fees) over the last 24h, 7d or 30d, with the change versus the prior period. Answers "top DeFi protocols by 30-day revenue" and "which protocols' revenue grew most". Filter by category (e.g. "Dexs", "Lending", "Liquid Staking") and/or chain. Each row: protocol slug, category, chains, revenue for the period, prior-period revenue, percent change, 24h/7d/30d totals and all-time total (USD). Source: DefiLlama, fees and revenue dataset. Pass a returned slug to defi_protocol_fees for the daily series.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category filter, case-insensitive, e.g. "Lending", "Dexs". |
| chain | string | – | Chain filter, case-insensitive, e.g. "Ethereum", "Solana". |
| data_type | string | – | Rank by revenue (default) or gross fees. |
| limit | number | – | Rows to return, 1-100. Default 20. |
| period | string | – | Window to rank on. Default "30d". |
| sort_by | string | – | "value" (default) ranks by period revenue; "change" ranks by percent change vs the prior period (protocols with under $10k prior-period revenue excluded). |
No output schema declared.
No examples provided.
defi_stablecoins ~32
Get stablecoin market cap and distribution across blockchains. Returns supply per chain to track adoption and network preferences.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
defi_token_emission ~150
One crypto token's full vesting / EMISSION SCHEDULE from DefiLlama (e.g. "Hyperliquid HYPE unlock schedule", "when do Arbitrum team tokens vest"). Returns max supply, allocation by category (insiders, airdrop, staking…) with % unlocked so far, per-recipient unlocked-now vs final amounts, the dated unlock events (past and upcoming, with USD value at the current price), and DefiLlama's methodology notes.
| Name | Type | Req | Description |
|---|---|---|---|
| protocol | string | yes | DefiLlama protocol slug or name (e.g. "hyperliquid", "arbitrum", "aptos", "sui"). Unknown names return close matches. |
No output schema declared.
No examples provided.
defi_token_unlocks ~280
Crypto token UNLOCK calendar from DefiLlama: every scheduled vesting cliff and emission-rate change across ~370 tracked tokens in a date window (e.g. "which token unlocks are scheduled this week", "unlocks over $10M between 2026-10-05 and 2026-10-12"). Returns per event: date, token, tokens unlocked, USD value at the current DefiLlama price (with the price time), share of circulating supply, and the recipients (investors, team, ecosystem…). Default window is today through 7 days out.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Window start, YYYY-MM-DD (UTC, inclusive). Default: today. |
| limit | number | – | Max events returned, sorted by date then USD value (default 100, max 500). |
| min_usd | number | – | Only cliff unlocks worth at least this many USD at the current price (e.g. 1000000). Excludes emission-rate changes, which have no single USD amount. |
| to | string | – | Window end, YYYY-MM-DD (UTC, inclusive). Default: from + 7 days. |
| token | string | – | Restrict to tokens whose name, symbol or DefiLlama slug contains this text (e.g. "hyperliquid", "ARB"). |
No output schema declared.
No examples provided.
defi_tvl_protocols ~87
Search DeFi protocols by name or category to compare their total value locked. Returns protocol name, TVL amount, blockchain, and category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category (e.g., "DEXes", "Lending", "Bridge", "CDP", "Yield") |
| search | string | – | Filter protocols by name (case-insensitive substring match) |
No output schema declared.
No examples provided.
defi_yields ~106
Find yield opportunities across DeFi pools filtered by project name, minimum TVL, or minimum APY. Returns APY, TVL, and project details.
| Name | Type | Req | Description |
|---|---|---|---|
| min_apy | number | – | Minimum APY percentage (e.g., 5 for 5%) |
| min_tvl | number | – | Minimum TVL in USD (e.g., 1000000 for $1M) |
| search | string | – | Filter by project name (case-insensitive substring match) |
No output schema declared.
No examples provided.
How do I install the Defillama MCP server?
Defillama runs locally as an npm package, launched with npx -y @pipeworx/mcp-defillama. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-defillama
claude mcp add pipeworx-io-defillama -- npx -y @pipeworx/mcp-defillama
What is the Defillama MCP server?
Defillama is an MCP server listed in the public MCP registry as io.github.pipeworx-io/defillama. DefiLlama MCP, DeFi analytics from DefiLlama (free, no auth). This page covers its npm package (@pipeworx/mcp-defillama).
Is the Defillama MCP server safe to use?
Defillama scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 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 Defillama MCP server expose?
Defillama exposes 9 tools: defi_tvl_protocols, defi_protocol_detail, defi_chain_tvl, defi_protocol_fees, defi_revenue_ranking, and 4 more. Their descriptions and schemas cost roughly 1,126 tokens of context every time the server is loaded.
Is the Defillama MCP server still maintained?
Defillama is still listed as active in the MCP registry. We last reached this channel on 6 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 Defillama MCP server under?
Defillama declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Defillama MCP server?
VerifyMCP ran 16 checks on Defillama, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.