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