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