mcp-health-checker

Audit MCP server health across configured endpoints and generate a read-only dashboard.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/FrogAi/Xenopus --skill mcp-health-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-health-checker
Source: https://github.com/FrogAi/Xenopus/tree/main/Gemini/Skills/Gemini%203.1%20Pro/mcp-health-checker
Command: npx skills add https://github.com/FrogAi/Xenopus --skill mcp-health-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The MCP health checker audits all configured MCP servers, surfacing real-time posture information and remediation guidance to prevent outages and misconfigurations.

Core Features & Use Cases

  • Live protocol handshake validation and capability enumeration across multiple transports (stdio, SSE, HTTP-streamable).
  • Read-only health dashboard with per-server status, versions, drift notes, and actionable remediation.
  • Secret hygiene and configuration hygiene checks to catch exposed credentials or misconfigurations.

Quick Start

Run the health-checker using your configured host client to survey MCP servers and generate a dashboard report.

Frequently Asked Questions about mcp-health-checker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit MCP server health across Claude Code and Cursor?

You can audit MCP server health by probing transports, initialization handshakes, and capabilities across settings.json, claude_desktop_config.json, and mcp.json paths to generate a read-only dashboard with per-server status.

What is the best way to check MCP servers for configuration drift and exposed secrets?

The best way to check MCP servers is to run automated secret hygiene and configuration drift checks, which surface exposed credentials and misconfigurations to prevent outages and provide actionable remediation.

Can I validate MCP protocol handshakes over stdio, SSE, and HTTP-streamable transports?

Yes, you can validate live protocol handshakes over stdio, SSE, and HTTP-streamable transports, enumerating server capabilities to accurately assess real-time posture and operational status.

Does the MCP health checker modify my live server configurations during diagnostics?

No, the MCP health checker is strictly read-only, probing endpoints and fetching live protocol data to output a diagnostic dashboard and remediation guidance without modifying your configurations.

How do I get a per-server status dashboard for my custom mcp.json endpoints?

You can get a per-server status dashboard by running the health checker against custom mcp.json paths, which performs live protocol fetches and outputs versions, drift notes, and actionable remediation.

Why does my MCP server initialization fail during health diagnostics?

MCP server initialization failures during health diagnostics are caused by misconfigured authentication, incorrect transport settings, or configuration drift, which the read-only dashboard surfaces with specific remediation steps.