The Openstatus MCP Health Checker is a tool designed to test Model Context Protocol (MCP) servers by acting exactly like a real AI client, such as Claude Desktop or Cursor. It solves the issue where a standard 200 OK from an HTTP ping is useless if the JSON-RPC handshake fails, which would cause an AI agent to break. The tool performs a true protocol-level validation instead of a basic uptime check.
Key features include executing the full spec-defined initialize, ping, and tools/list sequence for real handshakes. It provides deep visibility by allowing users to inspect exact JSON-RPC payloads, negotiated versions, and session IDs for zero-friction debugging. Additionally, it offers smart authentication by parsing RFC 9728 headers on 401 responses to surface exact token requirements when a server is locked down.
The tool works by running the complete protocol-level validation, simulating how a real AI client connects. It goes beyond connectivity checks to test the actual tool call flow, addressing edge cases that cause reliability issues in MCP integrations. This approach ensures the server is compliant and functional for production agent systems.
Benefits include ensuring AI agents can actually connect and use tools, not just that the server is alive. It helps developers debug MCP server issues by providing detailed insights into handshake failures and authentication requirements. The tool is particularly useful as MCP server quality varies, with many built against early spec drafts without standard compliance checks.
The target users are developers building or integrating MCP servers for AI agents. It is open-source and part of the synthetic monitoring gear at OpenStatus. The tool is a free, zero-install solution for testing MCP endpoints to verify protocol compliance and reliability.
Key Features
- •Full spec-defined initialize, ping, and tools/list sequence: The tool executes the exact JSON-RPC messages in the order required by the Model Context Protocol, including initialize to negotiate versions, ping to confirm connectivity, and tools/list to discover available tools. This ensures the server correctly implements the handshake, preventing silent failures in AI agent connections.
- •Deep visibility into JSON-RPC payloads, negotiated versions, and session IDs: Every message exchanged during the handshake is exposed in raw JSON-RPC format, allowing developers to inspect exactly what the server responded with. This zero-friction debugging capability helps identify mismatched versions, malformed responses, or missing capabilities that would cause agents to fail.