polymarket_edge_tracker — Agify MCP Tool
polymarket_edge_tracker
(polymarket edge tracker) is one of 38 tools on the
Agify
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call polymarket_edge_tracker from your client
- Claude Code Agify polymarket_edge_tracker run in your project directory
- Claude Desktop Agify polymarket_edge_tracker ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Agify polymarket_edge_tracker ~/.cursor/mcp.json
- VS Code Agify polymarket_edge_tracker .vscode/mcp.json
- Zed Agify polymarket_edge_tracker ~/.config/zed/settings.json
- Windsurf Agify polymarket_edge_tracker ~/.codeium/windsurf/mcp_config.json
- Cline Agify polymarket_edge_tracker ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Agify polymarket_edge_tracker ~/.gemini/settings.json
- Grok Agify polymarket_edge_tracker .mcp.json (in your project root)
- ChatGPT Agify polymarket_edge_tracker Settings → Connectors → Advanced → Developer mode
- Claude.ai Agify polymarket_edge_tracker Settings → Connectors → Add custom connector
- LangChain Agify polymarket_edge_tracker pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agify https://gateway.pipeworx.io/agify/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
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- 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
- predict_age
- predict_age_country
This list was read from the server itself, by connecting to it and calling tools/list on 24 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.