curve-mcp
Server Details
Curve - 43 tools for swap quotes, liquidity pools, and trading data
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- junct-bot/curve-mcp
- GitHub Stars
- 0
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 3.2/5 across 37 of 37 tools scored. Lowest: 2.1/5.
Many tools have overlapping purposes, causing significant ambiguity. For example, there are multiple tools for retrieving pools (get_pools_all, get_pools_big, get_pools_small, get_pools_empty) that differ only by TVL filters, and multiple tools for supply data (get_crvusd_total_supply, get_crvusd_total_supply_number) that differ only by output format. The descriptions help somewhat, but the boundaries between tools are often unclear, leading to potential misselection.
The naming follows a mostly consistent get_verb_noun pattern with snake_case throughout, which is predictable and readable. There are minor deviations, such as get_get_all_gauges (redundant 'get_get') and inconsistent use of underscores in some names (e.g., get_facto_gauges_crv_rewards_blockchain_id), but overall the convention is maintained across the set.
With 37 tools, the count is excessive for the apparent scope of querying Curve protocol data. Many tools appear to be variations of the same core operations (e.g., multiple pool retrieval tools with different filters), creating redundancy. This heavy toolset will likely overwhelm agents and complicate selection without adding proportional value.
The tool surface appears comprehensive for querying Curve protocol data, covering pools, gauges, volumes, APYs, supplies, and other metrics across chains and registries. There are minor gaps, such as limited write operations (e.g., no tools for interacting with contracts), but for a read-only API, it provides broad coverage of the domain with few dead ends.
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!