Merkl MCP Server
Related Servers
Alternatives to Merkl MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceUniversal MCP server for Mantle yield data, enabling users to fetch health status, dashboard summaries, and detailed opportunity information through natural language.7-
- AlicenseAqualityDmaintenanceMCP server for Hyperliquid that provides read-only on-chain wallet analytics. Enables natural-language queries about positions, fills, funding, and realized PnL for any public address.87 npmMIT
- AlicenseAqualityCmaintenanceAn MCP server that enables AI agents to query the Canton Network for balances, rewards, classified transactions, CC prices, and directory information using natural language.968 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Taskmarket onchain task marketplace on Base L2. Enables AI agents to discover, browse, create, claim, and submit work to Taskmarket through natural language.MIT
- AlicenseAqualityCmaintenanceMCP server that exposes unified AI-friendly tools over Messari's standardized lending subgraphs on The Graph. One natural-language query → fan out across 40+ lending protocols on multiple chains → get back structured, comparable data.197 npm1MIT
- AlicenseBqualityCmaintenanceMCP server to query Polymarket prediction market data via The Graph subgraphs and REST APIs, enabling AI agents to search markets, get live prices, order books, on-chain analytics, and trader profiles.3277 npmMIT
TDQS
Scored across 13 tools
Most tools are clearly separated by resource (campaigns vs opportunities) and action (search, get, count). The aggregate/max/min family is slightly overlapping in purpose, and get-current-timestamp is unrelated to the domain, but an agent can still distinguish the primary operations.
The set uses kebab-case consistently and mostly follows a predictable resource-action or resource-subresource-action pattern. The main deviation is get-current-timestamp, which reverses the verb-noun ordering used elsewhere.
With 13 tools, the server is well-scoped for a read-only API surface covering campaigns and opportunities. Each tool maps to a distinct query capability without excessive bloat.
The surface covers search, get, count, aggregation, and bin queries for opportunities, plus search/get/count for campaigns. It appears complete for a read-only API, though a few less-common query endpoints may still be missing.