check_health — Polystrike MCP Tool Read-only
check_health
(check health) is one of 8 tools on the
Polystrike
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_health from your client
- Claude Code Polystrike check_health run in your project directory
- Claude Desktop Polystrike check_health ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Polystrike check_health ~/.cursor/mcp.json
- VS Code Polystrike check_health .vscode/mcp.json
- Zed Polystrike check_health ~/.config/zed/settings.json
- Windsurf Polystrike check_health ~/.codeium/windsurf/mcp_config.json
- Cline Polystrike check_health ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Polystrike check_health ~/.gemini/settings.json
- Grok Polystrike check_health .mcp.json (in your project root)
- ChatGPT Polystrike check_health Settings → Connectors → Advanced → Developer mode
- Claude.ai Polystrike check_health Settings → Connectors → Add custom connector
- LangChain Polystrike check_health pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http polystrike https://polystrike.xyz/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.