nfl_edge — Prediction Markets Quant MCP Tool
nfl_edge
(nfl edge) is one of 29 tools on the
Prediction Markets Quant
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call nfl_edge from your client
- Claude Code Prediction Markets Quant nfl_edge run in your project directory
- Claude Desktop Prediction Markets Quant nfl_edge ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Prediction Markets Quant nfl_edge ~/.cursor/mcp.json
- VS Code Prediction Markets Quant nfl_edge .vscode/mcp.json
- Zed Prediction Markets Quant nfl_edge ~/.config/zed/settings.json
- Windsurf Prediction Markets Quant nfl_edge ~/.codeium/windsurf/mcp_config.json
- Cline Prediction Markets Quant nfl_edge ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Prediction Markets Quant nfl_edge ~/.gemini/settings.json
- Grok Prediction Markets Quant nfl_edge .mcp.json (in your project root)
- ChatGPT Prediction Markets Quant nfl_edge Settings → Connectors → Advanced → Developer mode
- Claude.ai Prediction Markets Quant nfl_edge Settings → Connectors → Add custom connector
- LangChain Prediction Markets Quant nfl_edge pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http quant https://predictionmarketspicks.com/api/mcp/mcpOther tools on this server
- fed_rate_odds
- calculate_ev
- kelly_size
- bayes_update
- convert_probability
- base_rate_gap
- combo_edge
- nfl_power_ratings
- nfl_win_probability
- find_arbitrage
- market_pulse
- commodity_edge
- scan_mispricings
- edge_alerts
- nfl_prop_edge
- nfl_prop_board
- nfl_ladder
- ladder_arb
- senate_map
- race_odds
- draft_board
- best_available
- player_outlook
- explain_player
- compare_players
- sleepers_and_busts
- who_do_i_draft
- adp_market_gaps
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.