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