settled_events — Settled MCP Tool
settled_events
(settled events) is one of 18 tools on the
Settled
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call settled_events from your client
- Claude Code Settled settled_events run in your project directory
- Claude Desktop Settled settled_events ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Settled settled_events ~/.cursor/mcp.json
- VS Code Settled settled_events .vscode/mcp.json
- Zed Settled settled_events ~/.config/zed/settings.json
- Windsurf Settled settled_events ~/.codeium/windsurf/mcp_config.json
- Cline Settled settled_events ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Settled settled_events ~/.gemini/settings.json
- Grok Settled settled_events .mcp.json (in your project root)
- ChatGPT Settled settled_events Settings → Connectors → Advanced → Developer mode
- Claude.ai Settled settled_events Settings → Connectors → Add custom connector
- LangChain Settled settled_events pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http settled https://settled.tools/mcpOther tools on this server
- settled_status
- settled_peek
- settled_submit
- settled_report
- settled_sellers
- settled_claim
- settled_preflight
- settled_check
- settled_find_endpoints
- settled_seller_reputation
- settled_income_venues
- settled_income_listings
- settled_income_check
- settled_watch
- settled_watch_alerts
- settled_weekly_report
- settled_verify
This list was read from the server itself, by connecting to it and calling tools/list on 3 October 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.