check_connection — Vibenate MCP Tool Read-only
check_connection
(check connection) 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 check_connection from your client
- Claude Code Vibenate check_connection run in your project directory
- Claude Desktop Vibenate check_connection ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Vibenate check_connection ~/.cursor/mcp.json
- VS Code Vibenate check_connection .vscode/mcp.json
- Zed Vibenate check_connection ~/.config/zed/settings.json
- Windsurf Vibenate check_connection ~/.codeium/windsurf/mcp_config.json
- Cline Vibenate check_connection ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Vibenate check_connection ~/.gemini/settings.json
- Grok Vibenate check_connection .mcp.json (in your project root)
- ChatGPT Vibenate check_connection Settings → Connectors → Advanced → Developer mode
- Claude.ai Vibenate check_connection Settings → Connectors → Add custom connector
- LangChain Vibenate check_connection 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.