mcp-http-diagnostics

Probe MCP Streamable HTTP endpoints via initialize and tools/list.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Randy-C-X/allanyiin_skills --skill mcp-http-diagnostics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-http-diagnostics
Source: https://github.com/Randy-C-X/allanyiin_skills/tree/main/skills/mcp-http-diagnostics
Command: npx skills add https://github.com/Randy-C-X/allanyiin_skills --skill mcp-http-diagnostics

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps operators quickly verify that a user-provided MCP Streamable HTTP endpoint is reachable, negotiates a proper protocol, and retrieves the tool catalog, enabling fast issue diagnosis without diving into server internals.

Core Features & Use Cases

  • Validate a given HTTP MCP URL by performing a deterministic initialize handshake and then query tools/list to present a clear tool set and protocol version.
  • Distinguish remote endpoint viability from host registry status, and provide actionable next steps when failures occur.
  • Support protocol version fallbacks and session management to maximize successful handshakes across MCP versions.

Quick Start

Provide the exact /mcp URL and run the deterministic probe to obtain a session id, protocol version, and the tool list.

Frequently Asked Questions about mcp-http-diagnostics

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

FAQPage Schema
How do I verify if my MCP Streamable HTTP endpoint is reachable and ready?

Verify MCP Streamable HTTP endpoints by running a deterministic initialize handshake and tools/list query to retrieve the protocol version, session id, and tool catalog, ensuring the endpoint is ready for use.

What is the process to list available tools from an MCP Streamable HTTP server?

Listing tools from an MCP Streamable HTTP server requires performing a deterministic initialize handshake to negotiate the protocol version, followed by a tools/list query to retrieve and present the complete tool metadata.

Can I check remote endpoint viability separately from host registry status?

Yes, you can distinguish remote endpoint viability from host registry status by probing the provided URL directly, which helps isolate connection failures from host registration issues and provides actionable next steps.

How do I handle protocol version fallbacks during an MCP initialize handshake?

Handle protocol version fallbacks during the MCP initialize handshake by applying session management and version negotiation logic, maximizing successful connections across different MCP Streamable HTTP server versions.

What should I provide to start diagnosing MCP Streamable HTTP connection issues?

Provide the exact /mcp URL of your endpoint to run the deterministic probe, which outputs the session id, protocol version, and tool list needed to diagnose connection or negotiation issues.