polymarket_arbitrage — Cisa Kev MCP Tool
polymarket_arbitrage
(polymarket arbitrage) is one of 40 tools on the
Cisa Kev
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call polymarket_arbitrage from your client
- Claude Code Cisa Kev polymarket_arbitrage run in your project directory
- Claude Desktop Cisa Kev polymarket_arbitrage ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Cisa Kev polymarket_arbitrage ~/.cursor/mcp.json
- VS Code Cisa Kev polymarket_arbitrage .vscode/mcp.json
- Zed Cisa Kev polymarket_arbitrage ~/.config/zed/settings.json
- Windsurf Cisa Kev polymarket_arbitrage ~/.codeium/windsurf/mcp_config.json
- Cline Cisa Kev polymarket_arbitrage ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Cisa Kev polymarket_arbitrage ~/.gemini/settings.json
- Grok Cisa Kev polymarket_arbitrage .mcp.json (in your project root)
- ChatGPT Cisa Kev polymarket_arbitrage Settings → Connectors → Advanced → Developer mode
- Claude.ai Cisa Kev polymarket_arbitrage Settings → Connectors → Add custom connector
- LangChain Cisa Kev polymarket_arbitrage pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http cisa-kev https://gateway.pipeworx.io/cisa-kev/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_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
- catalog
- entry
- vendors
- recent
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.