polymarket_fill_risk — Amplitude MCP Tool
polymarket_fill_risk
(polymarket fill risk) is one of 41 tools on the
Amplitude
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 Amplitude polymarket_fill_risk run in your project directory
- Claude Desktop Amplitude polymarket_fill_risk ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Amplitude polymarket_fill_risk ~/.cursor/mcp.json
- VS Code Amplitude polymarket_fill_risk .vscode/mcp.json
- Zed Amplitude polymarket_fill_risk ~/.config/zed/settings.json
- Windsurf Amplitude polymarket_fill_risk ~/.codeium/windsurf/mcp_config.json
- Cline Amplitude polymarket_fill_risk ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Amplitude polymarket_fill_risk ~/.gemini/settings.json
- Grok Amplitude polymarket_fill_risk .mcp.json (in your project root)
- ChatGPT Amplitude polymarket_fill_risk Settings → Connectors → Advanced → Developer mode
- Claude.ai Amplitude polymarket_fill_risk Settings → Connectors → Add custom connector
- LangChain Amplitude polymarket_fill_risk pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http amplitude https://gateway.pipeworx.io/amplitude/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
- amp_get_events
- amp_get_active_users
- amp_get_retention
- amp_user_search
- amp_get_user_activity
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.