bet_research — Dwd Climate MCP Tool
bet_research
(bet research) is one of 43 tools on the
Dwd Climate
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call bet_research from your client
- Claude Code Dwd Climate bet_research run in your project directory
- Claude Desktop Dwd Climate bet_research ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Dwd Climate bet_research ~/.cursor/mcp.json
- VS Code Dwd Climate bet_research .vscode/mcp.json
- Zed Dwd Climate bet_research ~/.config/zed/settings.json
- Windsurf Dwd Climate bet_research ~/.codeium/windsurf/mcp_config.json
- Cline Dwd Climate bet_research ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Dwd Climate bet_research ~/.gemini/settings.json
- Grok Dwd Climate bet_research .mcp.json (in your project root)
- ChatGPT Dwd Climate bet_research Settings → Connectors → Advanced → Developer mode
- Claude.ai Dwd Climate bet_research Settings → Connectors → Add custom connector
- LangChain Dwd Climate bet_research pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http dwd-climate https://gateway.pipeworx.io/dwd-climate/mcpOther tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- scan_dependency
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- archive_evidence
- archive_compare
- research_row
- classify_row
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- dwd_stations
- dwd_daily
- dwd_latest
This list was read from the server itself, by connecting to it and calling tools/list on 12 October 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.