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