Live LP analytics — Uniswap V2/V3, Balancer, Curve stableswap: PnL, health, slippage, depeg risk.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
AnalyzeBalancerLP2 fields changedInput schema / properties / pool_type / descriptionPrevious value: -"Which protocol the pool address belongs to: 'uniswap_v2' | 'uniswap_v3' | 'balancer' (2-asset weighted pool) | 'stableswap' (2-asset plain Curve pool). Must match the tool: the position/price/health/rug/slippage Uniswap tools take uniswap_v2|uniswap_v3; the Balancer tools take balancer; the Stableswap/depeg tools take stableswap."New value: +"Which protocol the pool at pool_address belongs to. This tool accepts only balancer (2-asset weighted pool)."Input schema / properties / pool_type / enumPrevious value: -[
- "uniswap_v2",
- "uniswap_v3",
- "balancer",
- "stableswap"
-]New value: +[
+ "balancer"
+]AnalyzePosition2 fields changedInput schema / properties / pool_type / descriptionPrevious value: -"Which protocol the pool address belongs to: 'uniswap_v2' | 'uniswap_v3' | 'balancer' (2-asset weighted pool) | 'stableswap' (2-asset plain Curve pool). Must match the tool: the position/price/health/rug/slippage Uniswap tools take uniswap_v2|uniswap_v3; the Balancer tools take balancer; the Stableswap/depeg tools take stableswap."New value: +"Which protocol the pool at pool_address belongs to. This tool accepts uniswap_v2 | uniswap_v3."Input schema / properties / pool_type / enumPrevious value: -[
- "uniswap_v2",
- "uniswap_v3",
- "balancer",
- "stableswap"
-]New value: +[
+ "uniswap_v2",
+ "uniswap_v3"
+]AnalyzeStableswapLP2 fields changedInput schema / properties / pool_type / descriptionPrevious value: -"Which protocol the pool address belongs to: 'uniswap_v2' | 'uniswap_v3' | 'balancer' (2-asset weighted pool) | 'stableswap' (2-asset plain Curve pool). Must match the tool: the position/price/health/rug/slippage Uniswap tools take uniswap_v2|uniswap_v3; the Balancer tools take balancer; the Stableswap/depeg tools take stableswap."New value: +"Which protocol the pool at pool_address belongs to. This tool accepts only stableswap (2-asset plain Curve pool)."Input schema / properties / pool_type / enumPrevious value: -[
- "uniswap_v2",
- "uniswap_v3",
- "balancer",
- "stableswap"
-]New value: +[
+ "stableswap"
+]AssessDepegRisk2 fields changedInput schema / properties / pool_type / descriptionPrevious value: -"Which protocol the pool address belongs to: 'uniswap_v2' | 'uniswap_v3' | 'balancer' (2-asset weighted pool) | 'stableswap' (2-asset plain Curve pool). Must match the tool: the position/price/health/rug/slippage Uniswap tools take uniswap_v2|uniswap_v3; the Balancer tools take balancer; the Stableswap/depeg tools take stableswap."New value: +"Which protocol the pool at pool_address belongs to. This tool accepts only stableswap (2-asset plain Curve pool)."Input schema / properties / pool_type / enumPrevious value: -[
- "uniswap_v2",
- "uniswap_v3",
- "balancer",
- "stableswap"
-]New value: +[
+ "stableswap"
+]BuildStateTwinCalculateSlippage4 fields changedInput schema / properties / amounts_inAdded value: +{
+ "description": "Optional batch form of 'amount_in': an array of values to evaluate in a single call. The pool is read once and the result is an array with one entry per element, in input order. Supply EITHER 'amount_in' (single) OR 'amounts_in' (batch), not both. Max 256 entries.",
+ "items": {
+ "type": "number"
+ },
+ "maxItems": 256,
+ "type": "array"
+}Input schema / properties / pool_type / descriptionPrevious value: -"Which protocol the pool address belongs to: 'uniswap_v2' | 'uniswap_v3' | 'balancer' (2-asset weighted pool) | 'stableswap' (2-asset plain Curve pool). Must match the tool: the position/price/health/rug/slippage Uniswap tools take uniswap_v2|uniswap_v3; the Balancer tools take balancer; the Stableswap/depeg tools take stableswap."New value: +"Which protocol the pool at pool_address belongs to. This tool accepts uniswap_v2 | uniswap_v3."Input schema / properties / pool_type / enumPrevious value: -[
- "uniswap_v2",
- "uniswap_v3",
- "balancer",
- "stableswap"
-]New value: +[
+ "uniswap_v2",
+ "uniswap_v3"
+]Input schema / requiredPrevious value: -[
- "amount_in",
- "pool_address",
- "rpc_url",
- "pool_type",
- "token_in_name"
-]New value: +[
+ "pool_address",
+ "rpc_url",
+ "pool_type",
+ "token_in_name"
+]CheckPoolHealth2 fields changedInput schema / properties / pool_type / descriptionPrevious value: -"Which protocol the pool address belongs to: 'uniswap_v2' | 'uniswap_v3' | 'balancer' (2-asset weighted pool) | 'stableswap' (2-asset plain Curve pool). Must match the tool: the position/price/health/rug/slippage Uniswap tools take uniswap_v2|uniswap_v3; the Balancer tools take balancer; the Stableswap/depeg tools take stableswap."New value: +"Which protocol the pool at pool_address belongs to. This tool accepts uniswap_v2 | uniswap_v3."Input schema / properties / pool_type / enumPrevious value: -[
- "uniswap_v2",
- "uniswap_v3",
- "balancer",
- "stableswap"
-]New value: +[
+ "uniswap_v2",
+ "uniswap_v3"
+]DetectRugSignals2 fields changedInput schema / properties / pool_type / descriptionPrevious value: -"Which protocol the pool address belongs to: 'uniswap_v2' | 'uniswap_v3' | 'balancer' (2-asset weighted pool) | 'stableswap' (2-asset plain Curve pool). Must match the tool: the position/price/health/rug/slippage Uniswap tools take uniswap_v2|uniswap_v3; the Balancer tools take balancer; the Stableswap/depeg tools take stableswap."New value: +"Which protocol the pool at pool_address belongs to. This tool accepts uniswap_v2 | uniswap_v3."Input schema / properties / pool_type / enumPrevious value: -[
- "uniswap_v2",
- "uniswap_v3",
- "balancer",
- "stableswap"
-]New value: +[
+ "uniswap_v2",
+ "uniswap_v3"
+]SimulateBalancerMove4 fields changedInput schema / properties / pool_type / descriptionPrevious value: -"Which protocol the pool address belongs to: 'uniswap_v2' | 'uniswap_v3' | 'balancer' (2-asset weighted pool) | 'stableswap' (2-asset plain Curve pool). Must match the tool: the position/price/health/rug/slippage Uniswap tools take uniswap_v2|uniswap_v3; the Balancer tools take balancer; the Stableswap/depeg tools take stableswap."New value: +"Which protocol the pool at pool_address belongs to. This tool accepts only balancer (2-asset weighted pool)."Input schema / properties / pool_type / enumPrevious value: -[
- "uniswap_v2",
- "uniswap_v3",
- "balancer",
- "stableswap"
-]New value: +[
+ "balancer"
+]Input schema / properties / price_change_pctsAdded value: +{
+ "description": "Optional batch form of 'price_change_pct': an array of values to evaluate in a single call. The pool is read once and the result is an array with one entry per element, in input order. Supply EITHER 'price_change_pct' (single) OR 'price_change_pcts' (batch), not both. Max 256 entries.",
+ "items": {
+ "type": "number"
+ },
+ "maxItems": 256,
+ "type": "array"
+}Input schema / requiredPrevious value: -[
- "price_change_pct",
- "lp_init_amt",
- "pool_address",
- "rpc_url",
- "pool_type"
-]New value: +[
+ "lp_init_amt",
+ "pool_address",
+ "rpc_url",
+ "pool_type"
+]SimulatePriceMove4 fields changedInput schema / properties / pool_type / descriptionPrevious value: -"Which protocol the pool address belongs to: 'uniswap_v2' | 'uniswap_v3' | 'balancer' (2-asset weighted pool) | 'stableswap' (2-asset plain Curve pool). Must match the tool: the position/price/health/rug/slippage Uniswap tools take uniswap_v2|uniswap_v3; the Balancer tools take balancer; the Stableswap/depeg tools take stableswap."New value: +"Which protocol the pool at pool_address belongs to. This tool accepts uniswap_v2 | uniswap_v3."Input schema / properties / pool_type / enumPrevious value: -[
- "uniswap_v2",
- "uniswap_v3",
- "balancer",
- "stableswap"
-]New value: +[
+ "uniswap_v2",
+ "uniswap_v3"
+]Input schema / properties / price_change_pctsAdded value: +{
+ "description": "Optional batch form of 'price_change_pct': an array of values to evaluate in a single call. The pool is read once and the result is an array with one entry per element, in input order. Supply EITHER 'price_change_pct' (single) OR 'price_change_pcts' (batch), not both. Max 256 entries.",
+ "items": {
+ "type": "number"
+ },
+ "maxItems": 256,
+ "type": "array"
+}Input schema / requiredPrevious value: -[
- "price_change_pct",
- "position_size_lp",
- "pool_address",
- "rpc_url",
- "pool_type"
-]New value: +[
+ "position_size_lp",
+ "pool_address",
+ "rpc_url",
+ "pool_type"
+]SimulateStableswapMove4 fields changedInput schema / properties / pool_type / descriptionPrevious value: -"Which protocol the pool address belongs to: 'uniswap_v2' | 'uniswap_v3' | 'balancer' (2-asset weighted pool) | 'stableswap' (2-asset plain Curve pool). Must match the tool: the position/price/health/rug/slippage Uniswap tools take uniswap_v2|uniswap_v3; the Balancer tools take balancer; the Stableswap/depeg tools take stableswap."New value: +"Which protocol the pool at pool_address belongs to. This tool accepts only stableswap (2-asset plain Curve pool)."Input schema / properties / pool_type / enumPrevious value: -[
- "uniswap_v2",
- "uniswap_v3",
- "balancer",
- "stableswap"
-]New value: +[
+ "stableswap"
+]Input schema / properties / price_change_pctsAdded value: +{
+ "description": "Optional batch form of 'price_change_pct': an array of values to evaluate in a single call. The pool is read once and the result is an array with one entry per element, in input order. Supply EITHER 'price_change_pct' (single) OR 'price_change_pcts' (batch), not both. Max 256 entries.",
+ "items": {
+ "type": "number"
+ },
+ "maxItems": 256,
+ "type": "array"
+}Input schema / requiredPrevious value: -[
- "price_change_pct",
- "lp_init_amt",
- "pool_address",
- "rpc_url",
- "pool_type"
-]New value: +[
+ "lp_init_amt",
+ "pool_address",
+ "rpc_url",
+ "pool_type"
+]AnalyzeBalancerLPAnalyzeBalancerPositionAnalyzeStableswapLPAnalyzeStableswapPositionSimulateBalancerMoveSimulateBalancerPriceMoveSimulateStableswapMoveSimulateStableswapPriceMoveAnalyzeBalancerPositionAnalyzePosition3 fields changedInput schema / properties / pool_address / descriptionPrevious value: -"On-chain address of the Uniswap pool/pair to analyze. Required. Lowercase, uppercase, or checksum casing all work."New value: +"On-chain address of the pool/pair to analyze (Uniswap V2/V3 pair, Balancer weighted pool, or Curve stableswap pool). Required. Lowercase, uppercase, or checksum casing all work."Input schema / properties / pool_type / descriptionPrevious value: -"Which Uniswap protocol the pool address belongs to: 'uniswap_v2' or 'uniswap_v3'."New value: +"Which protocol the pool address belongs to: 'uniswap_v2' | 'uniswap_v3' | 'balancer' (2-asset weighted pool) | 'stableswap' (2-asset plain Curve pool). Must match the tool: the position/price/health/rug/slippage Uniswap tools take uniswap_v2|uniswap_v3; the Balancer tools take balancer; the Stableswap/depeg tools take stableswap."Input schema / properties / pool_type / enumPrevious value: -[
- "uniswap_v2",
- "uniswap_v3"
-]New value: +[
+ "uniswap_v2",
+ "uniswap_v3",
+ "balancer",
+ "stableswap"
+]AnalyzeStableswapPositionAssessDepegRiskCalculateSlippage3 fields changedInput schema / properties / pool_address / descriptionPrevious value: -"On-chain address of the Uniswap pool/pair to analyze. Required. Lowercase, uppercase, or checksum casing all work."New value: +"On-chain address of the pool/pair to analyze (Uniswap V2/V3 pair, Balancer weighted pool, or Curve stableswap pool). Required. Lowercase, uppercase, or checksum casing all work."Input schema / properties / pool_type / descriptionPrevious value: -"Which Uniswap protocol the pool address belongs to: 'uniswap_v2' or 'uniswap_v3'."New value: +"Which protocol the pool address belongs to: 'uniswap_v2' | 'uniswap_v3' | 'balancer' (2-asset weighted pool) | 'stableswap' (2-asset plain Curve pool). Must match the tool: the position/price/health/rug/slippage Uniswap tools take uniswap_v2|uniswap_v3; the Balancer tools take balancer; the Stableswap/depeg tools take stableswap."Input schema / properties / pool_type / enumPrevious value: -[
- "uniswap_v2",
- "uniswap_v3"
-]New value: +[
+ "uniswap_v2",
+ "uniswap_v3",
+ "balancer",
+ "stableswap"
+]CheckPoolHealth3 fields changedInput schema / properties / pool_address / descriptionPrevious value: -"On-chain address of the Uniswap pool/pair to analyze. Required. Lowercase, uppercase, or checksum casing all work."New value: +"On-chain address of the pool/pair to analyze (Uniswap V2/V3 pair, Balancer weighted pool, or Curve stableswap pool). Required. Lowercase, uppercase, or checksum casing all work."Input schema / properties / pool_type / descriptionPrevious value: -"Which Uniswap protocol the pool address belongs to: 'uniswap_v2' or 'uniswap_v3'."New value: +"Which protocol the pool address belongs to: 'uniswap_v2' | 'uniswap_v3' | 'balancer' (2-asset weighted pool) | 'stableswap' (2-asset plain Curve pool). Must match the tool: the position/price/health/rug/slippage Uniswap tools take uniswap_v2|uniswap_v3; the Balancer tools take balancer; the Stableswap/depeg tools take stableswap."Input schema / properties / pool_type / enumPrevious value: -[
- "uniswap_v2",
- "uniswap_v3"
-]New value: +[
+ "uniswap_v2",
+ "uniswap_v3",
+ "balancer",
+ "stableswap"
+]DetectRugSignals3 fields changedInput schema / properties / pool_address / descriptionPrevious value: -"On-chain address of the Uniswap pool/pair to analyze. Required. Lowercase, uppercase, or checksum casing all work."New value: +"On-chain address of the pool/pair to analyze (Uniswap V2/V3 pair, Balancer weighted pool, or Curve stableswap pool). Required. Lowercase, uppercase, or checksum casing all work."Input schema / properties / pool_type / descriptionPrevious value: -"Which Uniswap protocol the pool address belongs to: 'uniswap_v2' or 'uniswap_v3'."New value: +"Which protocol the pool address belongs to: 'uniswap_v2' | 'uniswap_v3' | 'balancer' (2-asset weighted pool) | 'stableswap' (2-asset plain Curve pool). Must match the tool: the position/price/health/rug/slippage Uniswap tools take uniswap_v2|uniswap_v3; the Balancer tools take balancer; the Stableswap/depeg tools take stableswap."Input schema / properties / pool_type / enumPrevious value: -[
- "uniswap_v2",
- "uniswap_v3"
-]New value: +[
+ "uniswap_v2",
+ "uniswap_v3",
+ "balancer",
+ "stableswap"
+]SimulateBalancerPriceMoveSimulatePriceMove3 fields changedInput schema / properties / pool_address / descriptionPrevious value: -"On-chain address of the Uniswap pool/pair to analyze. Required. Lowercase, uppercase, or checksum casing all work."New value: +"On-chain address of the pool/pair to analyze (Uniswap V2/V3 pair, Balancer weighted pool, or Curve stableswap pool). Required. Lowercase, uppercase, or checksum casing all work."Input schema / properties / pool_type / descriptionPrevious value: -"Which Uniswap protocol the pool address belongs to: 'uniswap_v2' or 'uniswap_v3'."New value: +"Which protocol the pool address belongs to: 'uniswap_v2' | 'uniswap_v3' | 'balancer' (2-asset weighted pool) | 'stableswap' (2-asset plain Curve pool). Must match the tool: the position/price/health/rug/slippage Uniswap tools take uniswap_v2|uniswap_v3; the Balancer tools take balancer; the Stableswap/depeg tools take stableswap."Input schema / properties / pool_type / enumPrevious value: -[
- "uniswap_v2",
- "uniswap_v3"
-]New value: +[
+ "uniswap_v2",
+ "uniswap_v3",
+ "balancer",
+ "stableswap"
+]SimulateStableswapPriceMoveAnalyzePositionCalculateSlippageCheckPoolHealthDetectRugSignalsSimulatePriceMoveClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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.
No comments yet. Be the first to start the discussion!
Live LP analytics — Uniswap V2/V3, Balancer, Curve stableswap: PnL, health, slippage, depeg risk.
DeFi protocol data: TVL, yield pools, and cross-chain analytics
DefiLlama MCP — DeFi analytics from DefiLlama (free, no auth)
Solana + EVM liquidity-pool scores: Enter/Hold/Exit verdicts and 0-100 Wealthville Score.
Add one secure layer between your agents and this server.
Each tool targets a specific protocol and operation (e.g., AnalyzeBalancerLP for Balancer PnL, SimulatePriceMove for Uniswap price projection), with clear boundaries. Even tools that overlap in domain (like AnalyzeStableswapLP and AssessDepegRisk) are distinguished by purpose and output.
All tool names follow a consistent PascalCase verb_noun pattern (e.g., AnalyzeBalancerLP, CalculateSlippage, DetectRugSignals), making the tool surface predictable for an agent.
With 11 tools covering multiple protocols (Uniswap, Balancer, Curve) and operations (analysis, simulation, health check, risk detection), the count is well-scoped and each tool serves a distinct purpose without redundancy.
The server covers core analytics for three protocols but lacks health check and rug detection for Balancer and Curve pools, and slippage calculation is only available for Uniswap. These are notable gaps that limit the server's completeness for a multi-protocol DeFi analyzer.
