Openstatus MCP Health Checker

Product Introduction

1. Definition: The Openstatus MCP Health Checker is a free, browser-based diagnostic tool designed to perform a complete protocol-level health check on a Model Context Protocol (MCP) server. It belongs to the technical category of API and protocol monitoring and validation tools.
2. Core Value Proposition: It exists to solve the critical gap where traditional HTTP uptime monitors fail. While a standard ping can confirm a server is online, it cannot verify that the server correctly implements the MCP JSON-RPC specification. This tool ensures an MCP endpoint is not just reachable, but fully operational and ready for AI clients like Claude Desktop, Cursor, or custom agents by executing the exact handshake sequence they use.

Main Features

1. Full MCP Handshake Execution: The tool sequentially sends the three JSON-RPC calls mandated by the MCP specification for client initialization. It sends an initialize request (declaring protocol version 2025-06-18), a notifications/initialized notification, and then runs ping and tools/list requests in parallel using the captured session ID. This mirrors the exact behavior of a real MCP client, providing a true functional test.
2. Deep Protocol Inspection & Visibility: Each step of the handshake is recorded and displayed. Users can click on any step to inspect the exact JSON-RPC request payload sent and the full JSON-RPC response received, including negotiated protocol versions, server info, capabilities, and the Mcp-Session-Id. This granular visibility is essential for debugging protocol-level issues.
3. Intelligent OAuth 2.0 (RFC 9728) Authentication Parsing: When a server returns a 401 Unauthorized status, the tool automatically parses the WWW-Authenticate header. It extracts the resource_metadata URL, fetches the OAuth 2.0 Protected Resource Metadata document, and surfaces the authorized token endpoint. This guides users to the exact location to obtain a valid Bearer token, eliminating guesswork in configuring authentication for MCP servers.

Problems Solved

1. Pain Point: The inadequacy of basic HTTP status code monitoring for complex JSON-RPC APIs. A server can return 200 OK with an HTML error page or a misconfigured load balancer response, which would pass a simple uptime check but fail catastrophically for an MCP client. This leads to false positives and undetected service degradation.
2. Target Audience: MCP server developers and operators, DevOps/SRE teams managing AI tooling infrastructure, and AI application developers integrating with third-party MCP servers who need to verify endpoint compatibility and health before deployment or during incidents.
3. Use Cases: Essential for pre-deployment validation of a new MCP server, continuous integration (CI) pipeline testing, diagnosing connectivity issues reported by AI clients, and verifying the impact of server upgrades (e.g., checking for protocol version changes or broken methods).

Unique Advantages

1. Differentiation: Unlike generic HTTP ping services (e.g., standard uptime monitors) or simple curl commands, this tool speaks the MCP protocol natively. It validates the entire handshake flow, JSON-RPC ID echoing, method availability, and response structure, whereas competitors only validate network reachability and HTTP status codes.
2. Key Innovation: The integration of automated RFC 9728 OAuth metadata discovery within the health check workflow. This transforms a cryptic 401 error into an actionable, guided authentication setup flow, a feature not found in other API testing tools and critical for the secure, token-based access common in MCP deployments.

Frequently Asked Questions (FAQ)

1. What is the difference between an MCP health check and a regular HTTP ping? An HTTP ping only confirms a URL responds with a status code like 200, which could be from a load balancer or error page. An MCP health check performs the complete JSON-RPC handshake (initialize, ping, tools/list), validating that the server correctly implements the Model Context Protocol specification and is ready for AI clients.
2. How do I debug a 401 Unauthorized error from my MCP server? Use the Openstatus MCP Health Checker. It will detect the 401, parse the WWW-Authenticate header, and fetch the OAuth 2.0 resource metadata. The tool then displays the authorization server URL, telling you exactly where to obtain a Bearer token. Add this token as an Authorization header in the tool and re-run the check.
3. Is the Openstatus MCP Server Health Checker free to use? Yes, it is completely free, requires no account registration, and runs directly in your web browser. The check is executed from your session, and shared report links expire after 7 days, aligning with the open-source nature of the Openstatus platform.
4. Why does my MCP server health check fail even though it returns HTTP 200? This typically indicates the server endpoint is not correctly configured for MCP. A common failure is the server returning HTML (e.g., a default web page or proxy error) instead of valid JSON-RPC responses. The health check fails because it cannot parse the required JSON-RPC fields, such as the id or result, which an AI client would also fail on.