Most monitors just send an HTTP ping. But a 200 OK is useless if the JSON-RPC handshake fails. Our tool is different because it performs a true protocol-level check, acting exactly like a real AI client. Key features: Full Handshake: Executes the spec-defined initialize, ping, and tools/list sequence. Deep Visibility: Inspect exact JSON-RPC payloads and negotiated versions. Smart Auth: Parses RFC 9728 headers on 401s to surface exact token requirements.
Hey Product Hunt! 👋
Max and I are super excited to share this with you today.
As we've been diving into the Model Context Protocol (MCP) and building for AI agents, we kept running into the same frustrating issue: a standard 200 OK from an HTTP ping doesn't mean your AI client can actually connect. If the JSON-RPC handshake fails, or if the tools/list returns empty, your agent completely breaks.
We built the MCP Server Health Check to solve this. It's a free, zero-install tool that tests your endpoint exactly how a real AI client (like Claude Desktop or Cursor) would.
Instead of a basic uptime check, it performs a true protocol-level validation:
Real Handshakes: It runs the full spec-defined initialize, ping, and tools/list sequence.
Zero-Friction Debugging: You can click into any step to inspect the exact JSON-RPC payloads, negotiated versions, and session IDs.
Smart Auth: If your server is locked down, it parses RFC 9728 headers on a 401 to show you exactly where to fetch your auth token.
It’s completely open-source, just like the rest of our synthetic monitoring gear at OpenStatus.
Give it a spin with your own MCP endpoints (or test it out with a public one like [https://hf.co/mcp](https://hf.co...) and let us know what you think. We’ll be hanging out in the comments all day to answer your questions and hear your feedback! 🚀
when you say "like a real ai client" does it go through initialize → list-tools → actually call a tool, or stop at the handshake? in my experience the gap between "server responds to initialize" and "tools actually execute correctly" is where most bugs hide
@tibozaurus This is a useful direction for MCP reliability. A simple 200 OK doesn’t mean an agent can actually use the tool, so testing the real handshake and tools/list flow feels much closer to what production agent systems need.
timing on this is interesting because MCP server quality is all over the place right now. a lot of servers were built quickly against early drafts of the spec and there's no standard way to know if something is actually compliant until a client breaks on it. is there any plan to expose a compliance score or badge system so developers can signal to potential users that their server passed a real protocol check rather than just an uptime ping
smart approach testing MCP servers as a real client instead of just pinging endpoints. most of the reliability issues i've seen with MCP integrations come from edge cases in the actual tool call flow, not connectivity. curious if you're also testing for things like response format consistency across different server implementations?
About Openstatus MCP Health Checker on Product Hunt
“Test MCP servers like a real AI client, not just a ping”
Openstatus MCP Health Checker launched on Product Hunt on May 30th, 2026 and earned 161 upvotes and 12 comments, earning #3 Product of the Day. Most monitors just send an HTTP ping. But a 200 OK is useless if the JSON-RPC handshake fails. Our tool is different because it performs a true protocol-level check, acting exactly like a real AI client. Key features: Full Handshake: Executes the spec-defined initialize, ping, and tools/list sequence. Deep Visibility: Inspect exact JSON-RPC payloads and negotiated versions. Smart Auth: Parses RFC 9728 headers on 401s to surface exact token requirements.
Openstatus MCP Health Checker was featured in Open Source (68.4k followers), Developer Tools (513.2k followers), Artificial Intelligence (469.7k followers) and GitHub (41.2k followers) on Product Hunt. Together, these topics include over 200.3k products, making this a competitive space to launch in.
Who hunted Openstatus MCP Health Checker ?
Openstatus MCP Health Checker was hunted by fmerian. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Reviews
Openstatus MCP Health Checker has received 2 reviews on Product Hunt with an average rating of 5.00/5. Read all reviews on Product Hunt.
Want to see how Openstatus MCP Health Checker stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
fmerian