mcp-server-everesteer
Related Servers
Alternatives to mcp-server-everesteer
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLets AI assistants download competition training and inference data, submit predictions, backtest strategies on the meta-model, and check performance through natural language. It can be used as a hosted endpoint or run locally with an API key.778 PyPI9MIT

Futurykon MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceConnects AI agents to the Futurykon prediction platform, enabling them to query and interact with prediction questions, manage predictions, and view leaderboards.MIT- FlicenseNot gradedqualityDmaintenanceProvides agent-ready access to the Eigenlayer API through MCP, enabling natural language interaction with Eigenlayer protocols.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to safely interact with Ethereum by providing structured tools for reading blockchain state, simulating transactions, and drafting transactions that require human-in-the-loop approval.1-
- AlicenseCqualityBmaintenanceProvides Model Context Protocol and LangGraph/LangChain tools for reading Polymarket prediction-market and perpetual-futures data, inspecting accounts and positions, and using optional gated trading and transfer features.49MIT
- AlicenseAqualityBmaintenanceEnables AI agents to read dreamDEX perpetual markets, inspect portfolio state, claim testnet credit, and place safety-guarded on-chain orders on the Somnia Hideki testnet through MCP tool calls.7MIT
TDQS
Scored across 4 tools
Each tool targets a distinct concern: service health, capability index, scoring formula explanation, and authentication identity. The only mild overlap is between get_capabilities and explain_scoring, since both return live configuration/metadata rather than data operations, but descriptions clarify the split.
Three tools use snake_case but with inconsistent verb conventions (get_, explain_, and a bare whoami). The bare-noun whoami breaks the verb_noun pattern, though all names remain readable and unsurprising.
Four tools is thin for an API that apparently offers scoring, payouts, and compute. It reads as an introspection-only surface, leaving the primary domain actions unrepresented.
The entire surface is read-only metadata: health, capabilities, scoring rules, and identity. There is no tool to actually run a score, compute a payout, or submit anything, so an agent can learn the rules but cannot use the service's core function.