full_site_crawl — HolicAudit website checks MCP Tool
full_site_crawl
(full site crawl) is one of 6 tools on the
HolicAudit website checks
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call full_site_crawl from your client
- Claude Code HolicAudit website checks full_site_crawl run in your project directory
- Claude Desktop HolicAudit website checks full_site_crawl ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor HolicAudit website checks full_site_crawl ~/.cursor/mcp.json
- VS Code HolicAudit website checks full_site_crawl .vscode/mcp.json
- Zed HolicAudit website checks full_site_crawl ~/.config/zed/settings.json
- Windsurf HolicAudit website checks full_site_crawl ~/.codeium/windsurf/mcp_config.json
- Cline HolicAudit website checks full_site_crawl ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI HolicAudit website checks full_site_crawl ~/.gemini/settings.json
- Grok HolicAudit website checks full_site_crawl .mcp.json (in your project root)
- ChatGPT HolicAudit website checks full_site_crawl Settings → Connectors → Advanced → Developer mode
- Claude.ai HolicAudit website checks full_site_crawl Settings → Connectors → Add custom connector
- LangChain HolicAudit website checks full_site_crawl pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http website-checks https://audit.huutran.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 10 November 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.