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