bet_research — Wipo Ipc MCP Tool
bet_research
(bet research) is one of 45 tools on the
Wipo Ipc
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 Wipo Ipc bet_research run in your project directory
- Claude Desktop Wipo Ipc bet_research ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Wipo Ipc bet_research ~/.cursor/mcp.json
- VS Code Wipo Ipc bet_research .vscode/mcp.json
- Zed Wipo Ipc bet_research ~/.config/zed/settings.json
- Windsurf Wipo Ipc bet_research ~/.codeium/windsurf/mcp_config.json
- Cline Wipo Ipc bet_research ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Wipo Ipc bet_research ~/.gemini/settings.json
- Grok Wipo Ipc bet_research .mcp.json (in your project root)
- ChatGPT Wipo Ipc bet_research Settings → Connectors → Advanced → Developer mode
- Claude.ai Wipo Ipc bet_research Settings → Connectors → Add custom connector
- LangChain Wipo Ipc bet_research pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http wipo-ipc https://gateway.pipeworx.io/wipo-ipc/mcp
Other 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
- company_register_search
- 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
- ipc_lookup
- ipc_children
- ipc_search
- ipc_versions
This list was read from the server itself, by connecting to it and calling tools/list on 18 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.