MCP Health Check Specifications
Learn how MCPServerStatus performs rigorous, multi-stage protocol health checks on Model Context Protocol servers.
01 / URL Validation & SSRF Protection
Before attempting any connection, every submitted endpoint URL undergoes strict validation. We perform an active DNS lookup on the hostname and inspect every resolved IP address. Any address resolving to loopback, private networks, link-local, or cloud metadata endpoints is immediately rejected to prevent Server-Side Request Forgery (SSRF).
02 / Transport Negotiation & Connection
MCPServerStatus attempts to connect using Streamable HTTP Client Transport (modern) or Server-Sent Events (SSE) Client Transport. Strict timeouts (7 seconds) limit connections.
03 / Protocol Handshake & Tool Discovery
Once connected, the scanner exchanges initialization messages and optionally safely inspects tool metadata.
Security Guarantee: MCPServerStatus NEVER executes arbitrary MCP tools during health checks.