Defillama Mcp

io.github.srimisraPublished by GitHub account srimisrav1.0.0Updated Oct 24, 2026

DefiLlama MCP — TVL, yields, volumes, fees, and protocol analytics for DeFi.

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Gives an assistant read-only access to DeFi analytics from DefiLlama, including TVL, yields, volumes, fees, and protocol data.

What you can do
This remote MCP server exposes DefiLlama's DeFi analytics to an assistant. Based on the description, it covers total value locked (TVL), yield opportunities, trading volumes, fees, and protocol-level analytics. No individual tool names are listed in the available material, so the exact set of queries is not documented here.
When to use it
Useful when an assistant needs to answer questions or produce summaries about DeFi protocols, chain-level TVL, yield rates, volumes, or fees. It is meant for read-oriented research and reporting rather than for executing transactions.
Requirements
It runs as a remote streamable HTTP endpoint, so no local package or runtime is needed. The manifest declares no authentication, no environment variables, and no headers, and no accounts or API keys are mentioned. Network access to the endpoint is required.
Before you install
The manifest declares no credentials, so nothing secret is requested. The description indicates analytics and data retrieval only; no writing, sending, or deleting actions are described. Queries are sent to a third-party remote endpoint, so consider whether the questions you ask are appropriate to share with that service.

Installation

In SourceWeft

  1. Open Defillama Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.srimisra%2Fdefillama-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "defillama": {
      "type": "http",
      "url": "https://defillama.mcp.junct.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.