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