updown_venue_compare — Segment MCP Tool
updown_venue_compare
(updown venue compare) is one of 48 tools on the
Segment
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call updown_venue_compare from your client
- Claude Code Segment updown_venue_compare run in your project directory
- Claude Desktop Segment updown_venue_compare ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Segment updown_venue_compare ~/.cursor/mcp.json
- VS Code Segment updown_venue_compare .vscode/mcp.json
- Zed Segment updown_venue_compare ~/.config/zed/settings.json
- Windsurf Segment updown_venue_compare ~/.codeium/windsurf/mcp_config.json
- Cline Segment updown_venue_compare ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Segment updown_venue_compare ~/.gemini/settings.json
- Grok Segment updown_venue_compare .mcp.json (in your project root)
- ChatGPT Segment updown_venue_compare Settings → Connectors → Advanced → Developer mode
- Claude.ai Segment updown_venue_compare Settings → Connectors → Add custom connector
- LangChain Segment updown_venue_compare pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http segment https://gateway.pipeworx.io/segment/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
- company_register_search
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- prediction_calibration
- updown_divergence_rate
- 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
- segment_list_sources
- segment_source_destinations
- segment_list_destinations
- segment_list_warehouses
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.