MCP servers are fragile. A server can be listed on Smithery with glowing docs but be completely dead — returning 502s or timing out. I checked 50+ random MCP endpoints and 52% were unreachable.
MCP Health Monitor tests any MCP server endpoint, checks Smithery namespaces, and monitors uptime.
Tools
-
check_server(url)— Tests if an MCP endpoint responds -
check_smithery(namespace)— Scans all servers in a Smithery namespace -
monitor_add(url, interval)— Adds a server to your watchlist -
monitor_status()— Dashboard of all monitored servers
Why This Exists
Every MCP developer has had the experience of installing a server from a directory, configuring it, and getting silence. This tool catches that before you waste time on configuration.
Free tier: 20 checks per instance. Pro: $19/month.
GitHub: https://github.com/Rumblingb/mcp-health-monitor
Smithery: https://smithery.ai/server/vishar-rumbling/mcp-health-monitor
Pro: https://buy.stripe.com/aFafZj0qXck4bY43IL1oI0F