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