bet_research — Fca Register MCP Tool
bet_research
(bet research) is one of 40 tools on the
Fca Register
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 Fca Register bet_research run in your project directory
- Claude Desktop Fca Register bet_research ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Fca Register bet_research ~/.cursor/mcp.json
- VS Code Fca Register bet_research .vscode/mcp.json
- Zed Fca Register bet_research ~/.config/zed/settings.json
- Windsurf Fca Register bet_research ~/.codeium/windsurf/mcp_config.json
- Cline Fca Register bet_research ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Fca Register bet_research ~/.gemini/settings.json
- Grok Fca Register bet_research .mcp.json (in your project root)
- ChatGPT Fca Register bet_research Settings → Connectors → Advanced → Developer mode
- Claude.ai Fca Register bet_research Settings → Connectors → Add custom connector
- LangChain Fca Register bet_research pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http fca-register https://gateway.pipeworx.io/fca-register/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
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- fca_firm_search
- fca_firm_details
- fca_firm_representatives
- fca_individual_lookup
This list was read from the server itself, by connecting to it and calling tools/list on 25 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.