Problee MCP
OfficialRelated Servers
Alternatives to Problee MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables MCP-compatible AI agents to research and trade prediction markets on Polymarket and Kalshi, including market search, orderbooks, price history, positions, order routing, and on-chain builder-code attribution, plus overshoot and dispute-risk signals.42269 PyPIMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to discover prediction markets, view real-time data, execute trades (market/limit orders), and manage portfolios on Polymarket.630 npm3MIT
- AlicenseAqualityCmaintenanceEnables AI agents to discover and analyze prediction markets, execute trades, and manage positions on Polymarket via the Model Context Protocol.714 npm20MIT
- FlicenseNot gradedqualityDmaintenanceTrade and monitor prediction markets across Polymarket, Kalshi, Opinion, Limitless, and PredictFun from any AI agent. Unified real-time data, live orderbook streaming, and order execution — one API key, one interface, five exchanges.-
- AlicenseBqualityNot gradedmaintenanceEnables AI agents to interact with the Polymarket prediction market platform to discover markets, analyze real-time pricing, and monitor public portfolio data. It provides comprehensive access to market analytics, implied probabilities, and order books through the Model Context Protocol.5930 npm-
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with Polymarket prediction markets, including retrieving market data, user positions, and trading history.89 npm11Apache 2.0
TDQS
Scored across 31 tools
Most tools map to a distinct resource+action, and descriptions explicitly separate near-duplicates (e.g. get_market_state vs get_market_resolution_state, get_market_depth vs full orderbook). The main soft spot is a cluster of four event/webhook tools (list_event_types, list_webhook_event_types, discover_events, discover_webhooks) that require careful reading to tell apart, but their descriptions do distinguish them.
Every tool follows the same problee_<verb>_<noun> convention using consistent verbs (get, list, discover), with no camelCase or style mixing. Predictable and easy to scan.
31 tools is heavy and beyond the typical well-scoped band, though the domain (markets, trading, resolution, discovery, events, webhooks, protocol config) is genuinely broad so most tools earn a place. It sits at the borderline-to-heavy end rather than being clearly excessive.
Read/discovery coverage is thorough (markets, positions, balance, trades, resolution, leaderboard, fees, contracts, rules, events, webhooks). However the surface is heavily read-oriented: there is no explicit market-creation or trade-execution/prepare tool in the set, even though descriptions reference publishing surfaces and /trade/prepare, leaving notable write-path gaps.