prizepicksapi-mcp
Related Servers
Alternatives to prizepicksapi-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityCmaintenanceProvides MCP clients with sportsbook prices and pick'em lines across DraftKings, FanDuel, BetRivers, PrizePicks, Underdog and Pick6, including capture times and line history. Two tools work without an account, with the remainder requiring a free API key.9MIT- AlicenseAqualityBmaintenanceProvides tools for live sportsbook odds, player props, scores, football xG, historical closing lines, US horse racing entries and results, and prediction-market prices through a hosted endpoint and local stdio proxy.81MIT
- AlicenseAqualityBmaintenanceLive sports betting player props MCP server covering NBA, MLB, NFL, NHL, NCAA, and soccer. Unified from real sportsbooks into one REST API and a real MCP server (Streamable HTTP). Free tier, no card required.5MIT
- AlicenseNot gradedqualityCmaintenanceProps-first sports odds API with a hosted MCP server. Live odds and player props (moneyline, spreads, totals) across US sportsbooks, normalized to JSON. Tools: get_odds, get_props, get_events, get_books. API-key auth, free tier.MIT No Attribution
- FlicenseAqualityCmaintenanceUnofficial MCP server that exposes the PrijsProfeet API as validated tools for product search, price history, forecasts, deals, and matching. It can run via stdio or as an authenticated Streamable HTTP server.24-
- AlicenseAqualityBmaintenanceA local, single-user MCP server that tracks Path of Exile 2 market data and exposes it to an LLM, enabling currency price lookups, per-league price history, watchlists, stash valuation, and trade preparation from your own machine.151MIT
TDQS
Scored across 5 tools
Each tool targets a clearly distinct resource: demo projections, demo line history, demo change events, payout reference data, and credit-cost quoting. There is little chance of confusing one tool for another.
All names use readable snake_case and descriptive nouns, with a consistent demo_ prefix for the three demo endpoints. The set is not verb_noun based, but the convention remains predictable enough for an agent.
Five tools is well-scoped for a small demo/reference API surface, and each tool appears to serve a distinct purpose. There is no obvious bloat or missing count issue.
The surface is mostly demo/reference-only despite descriptions referencing live data, and there is no tool to actually run live projection, line history, or change-feed requests. credit_cost also quotes REST request costs without an accompanying request-execution tool, creating a notable dead end.