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