actually-mcp-server
Related Servers
Alternatives to actually-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to discover prediction markets, view real-time data, execute trades (market/limit orders), and manage portfolios on Polymarket.622 npm3MIT
- AlicenseAqualityDmaintenanceEnables AI agents to browse, search, and trade on Polymarket prediction markets, including viewing markets, order books, balances, and placing/canceling orders.119 npmMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with Polymarket prediction markets, including retrieving market data, user positions, and trading history.87 npm11Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Polymarket prediction markets through read-only access to market data, events, orderbooks, and user positions, plus authenticated trading capabilities for creating and managing orders.1-
- AlicenseBqualityDmaintenanceEnables LLM agents to interact with Polymarket prediction markets, including market discovery, real-time pricing, analytics, account management, and trading with built-in safety guards.34MIT
- AlicenseNot gradedqualityDmaintenanceEnables real-time access to Polymarket prediction market odds, allowing AI agents to retrieve events, markets, and search for predictions with formatted outputs.5MIT
TDQS
Scored across 2 tools
check_news takes natural language news text and returns a market anchor with a cached YES probability, while get_market requires a specific marketId and returns live market and orderbook data. The input types and outputs are distinct, and the description explicitly frames them as complementary rather than overlapping.
Both tool names follow the same snake_case verb_noun pattern: check_news and get_market. The verbs are simple and descriptive, with no mixed conventions or inconsistent styling.
Two tools is lean, but the server appears intentionally narrow: it maps news to a Polymarket market and provides live market data. Both tools are necessary for that workflow, making the count slightly small but still reasonable.
For the stated purpose, the tool surface is complete: check_news handles the news-to-market mapping, and get_market provides the live price and orderbook follow-up referenced by check_news. The primary workflow has no obvious dead ends.