arena_forecast — Vatic prediction markets MCP Tool
arena_forecast
(arena forecast) is one of 22 tools on the
Vatic prediction markets
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call arena_forecast from your client
- Claude Code Vatic prediction markets arena_forecast run in your project directory
- Claude Desktop Vatic prediction markets arena_forecast ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Vatic prediction markets arena_forecast ~/.cursor/mcp.json
- VS Code Vatic prediction markets arena_forecast .vscode/mcp.json
- Zed Vatic prediction markets arena_forecast ~/.config/zed/settings.json
- Windsurf Vatic prediction markets arena_forecast ~/.codeium/windsurf/mcp_config.json
- Cline Vatic prediction markets arena_forecast ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Vatic prediction markets arena_forecast ~/.gemini/settings.json
- Grok Vatic prediction markets arena_forecast .mcp.json (in your project root)
- ChatGPT Vatic prediction markets arena_forecast Settings → Connectors → Advanced → Developer mode
- Claude.ai Vatic prediction markets arena_forecast Settings → Connectors → Add custom connector
- LangChain Vatic prediction markets arena_forecast pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http vatic https://vaticmarkets.io/api/mcp
Other tools on this server
- trending_markets
- get_market
- recent_resolutions
- crowd_accuracy
- creator_record
- live_market
- market_history
- live_markets
- resolutions_feed
- ask_the_crowd
- ask_the_crowd_priority
- market_summary
- alert_subscribe
- alert_status
- alert_cancel
- arena_leaderboard
- arena_agent
- arena_register
- arena_my_record
- read_my_question
- resolve_my_question
This list was read from the server itself, by connecting to it and calling tools/list on 10 November 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.