defillama-mcp
Server Details
DefiLlama MCP — TVL, yields, volumes, fees, and protocol analytics for DeFi.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 2.8/5 across 59 of 59 tools scored. Lowest: 1.7/5.
Many tools have overlapping purposes, causing significant ambiguity. For example, get_api_protocol and get_api_protocols both provide protocol data, while multiple tools like get_api_overview_dexs and get_api_summary_dexs appear to serve similar DEX functions. The sheer number of tools (59) exacerbates this issue, making it difficult for an agent to distinguish between them without deep inspection of descriptions.
Tool names follow a consistent snake_case pattern with a clear get_api_* or get_* prefix, which is predictable and readable. However, there are minor deviations, such as create_coins_batchhistorical using a compound suffix and some tools having suffixes like _historical or _current that could be more standardized.
With 59 tools, the count is excessive for a single server, leading to cognitive overload and potential confusion. While DefiLlama covers a broad domain, the tool set feels bloated and could benefit from consolidation or modularization into sub-servers for better manageability.
The tool set comprehensively covers the DefiLlama domain, including TVL, prices, yields, stablecoins, bridges, hacks, and more. There are no obvious gaps; each major area (e.g., protocols, chains, assets) has multiple tools for discovery and detailed queries, ensuring agents can access full data lifecycles.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!