prediction-market-mcp
Related Servers
Alternatives to prediction-market-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for querying and optionally trading across prediction markets (Polymarket, Kalshi, Limitless, Manifold) through a unified API.31MIT
- AlicenseBqualityAmaintenanceMCP server for Polymarket prediction markets enabling query of markets, events, narratives, arbitrage, and more via MCP or HTTP.9MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI agents direct access to Polymarket Crypto prediction markets, enriched with live spot prices. Discover markets, analyze order books, paper trade strategies, track activity, and execute live trades — all through natural language.1AGPL 3.0
- AlicenseCqualityDmaintenanceMCP server exposing 47 Polymarket API tools for AI assistants. Covers the full Gamma, CLOB, and Data APIs plus a fluent MarketBuilder for multi-source queries.4782MIT
- AlicenseCqualityBmaintenanceMCP server that provides a unified prediction market API for multiple venues like Polymarket and Kalshi, allowing AI agents to discover markets, fetch order books, and execute trades through a single interface.32368MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that exposes Polymarket prediction markets via CLI wrapper. Enables AI agents to discover markets, check prices, and place trades programmatically.-
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose is clearly defined to fetch prediction market prices from specific sources.
Since there is only one tool, naming consistency is inherently perfect with no deviations or mixed conventions to evaluate. The tool name follows a clear verb_noun pattern (get-prediction-markets).
A single tool is too few for a server named 'prediction-market-mcp', which suggests a broader domain involving prediction markets. This minimal toolset limits functionality and likely leaves significant gaps in coverage, such as creating markets, placing bets, or managing accounts.
The tool surface is severely incomplete for the prediction market domain. It only provides a read operation (get prices) but lacks essential CRUD/lifecycle operations like creating markets, updating positions, or deleting entries, which are critical for agent workflows in this context.