mcp-http-diagnostics

Diagnose MCP Streamable HTTP endpoints and list available tools via initialize handshake.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/JustinChangTW/ai-skills-core --skill mcp-http-diagnostics-justinchangtw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcp-http-diagnostics
Source: https://github.com/JustinChangTW/ai-skills-core/tree/main/skills/09-software-problem-solving/mcp-http-diagnostics
Command: npx skills add https://github.com/JustinChangTW/ai-skills-core --skill mcp-http-diagnostics-justinchangtw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? When you have an MCP HTTP or Streamable HTTP endpoint URL and need to know whether it actually works, this Skill verifies connectivity and retrieves the authoritative tool list in seconds, avoiding wasted effort on wrong checks like bare GET /mcp requests or host-side resource listings. ## Core Features & Use Cases - Fast Handshake Verification: Performs POST initialize, captures Mcp-Session-Id and negotiated MCP-Protocol-Version, then calls tools/list for the authoritative tool inventory. - Structured Error Triage: Classifies failures such as 401 auth required, protocol version mismatch, session_not_found, and wrong endpoint, with concrete next steps for each. - Deterministic Probe Script: Ships a dependency-free Python script that handles endpoint normalization, protocol version fallback, and bearer token authentication. - Use Case: You receive a URL like http://127.0.0.1:9091/mcp and need to confirm it is alive and see what tools it exposes; the Skill runs initialize plus tools/list and reports the tool names, parameters, and negotiated protocol version. ## Quick Start Use the mcp-http-diagnostics skill to check whether this MCP endpoint http://127.0.0.1:9091/mcp is reachable and list all of its tools.

Frequently Asked Questions about mcp-http-diagnostics

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

FAQPage Schema
How do I check if an MCP Streamable HTTP endpoint is working?▼

Send a POST initialize request with a protocolVersion to the endpoint, then capture the Mcp-Session-Id and MCP-Protocol-Version response headers. Follow with a POST tools/list using those session headers to confirm the server is fully operational.

How to list tools from an MCP server over HTTP?▼

After a successful initialize handshake, send a POST tools/list JSON-RPC request to the same endpoint with the Mcp-Session-Id and negotiated MCP-Protocol-Version headers. The response contains tool names, descriptions, and required input parameters.

Why does GET /mcp return 400 or 406 errors?▼

GET /mcp is not a valid health check for Streamable HTTP servers because it requires an existing session and Accept: text/event-stream. A 400 or 406 response usually means the wrong request method was used, not that the server is down; use POST initialize instead.

What does protocol_version_mismatch mean in MCP?▼

It means the client and server disagree on the MCP protocol version. Ensure the header and body protocolVersion values match, then retry with fallback versions such as 2025-06-18, 2025-03-26, or 2024-11-05.

Can this tool fix or modify an MCP server implementation?▼

No, it only diagnoses connectivity and lists tools for user-provided endpoints. Designing, implementing, or refactoring MCP server code is explicitly out of scope and should be handed to a development-focused workflow.