zerodust_get_sweep_status — zerodust MCP Tool
zerodust_get_sweep_status
(zerodust get sweep status) is one of 7 tools on the
zerodust
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call zerodust_get_sweep_status from your client
- Claude Code zerodust zerodust_get_sweep_status run in your project directory
- Claude Desktop zerodust zerodust_get_sweep_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor zerodust zerodust_get_sweep_status ~/.cursor/mcp.json
- VS Code zerodust zerodust_get_sweep_status .vscode/mcp.json
- Zed zerodust zerodust_get_sweep_status ~/.config/zed/settings.json
- Windsurf zerodust zerodust_get_sweep_status ~/.codeium/windsurf/mcp_config.json
- Cline zerodust zerodust_get_sweep_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI zerodust zerodust_get_sweep_status ~/.gemini/settings.json
- Grok zerodust zerodust_get_sweep_status .mcp.json (in your project root)
- ChatGPT zerodust zerodust_get_sweep_status Settings → Connectors → Advanced → Developer mode
- Claude.ai zerodust zerodust_get_sweep_status Settings → Connectors → Add custom connector
- LangChain zerodust zerodust_get_sweep_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http zerodust https://api.zerodust.xyz/mcpOther tools on this server
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.