MCP health — MCP directory health check diagnostics

Diagnoses whether an MCP server is reachable, by live HTTP probe.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
90%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~168Tokens (tool definitions)
~411 BTypical response size
Minimal attention impact (0.13% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "probe": {
      "url": "https://mcp-health.rowb.app/mcp"
    }
  }
}

Remote endpoints

https://mcp-health.rowb.app/mcpstreamable-http

What it can do

Tool inventory

Tools (2)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢check_mcp_server(url)

Diagnose whether an MCP server passes directory health checks. Runs five real HTTP probes (modern initialize, legacy initialize, anonymous tools/list, unauthorized tools/call, WWW-Authenticate/resource_metadata) and returns findings with fixes.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "MCP endpoint URL (streamable HTTP)"
    }
  },
  "required": [
    "url"
  ]
}
🟢list_scan_results(verdict, limit)

List the most recent scan results across MCP servers taken from the official registry, with verdicts and issue counts.

Input Schema

{
  "type": "object",
  "properties": {
    "verdict": {
      "type": "string",
      "enum": [
        "pass",
        "warn",
        "fail"
      ],
      "description": "optional filter"
    },
    "limit": {
      "type": "number"
    }
  }
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded2 tools