mcp-validator

To validate an MCP endpoint, check that requests include jsonrpc = '2.0', a method, and an id, then verify responses contain a matching result or error with proper codes. This ensures your endpoint conforms to the 2024-11-05 specification and prevents client integration issues.

A correct JSON-RPC 2.0 response structure requires jsonrpc = '2.0', an id matching the request, and exactly one of a result or error field present with proper structure. This validation prevents malformed replies that break MCP client compatibility.

To validate MCP tool schemas, check that tool names are unique, descriptions are clear, and inputSchema is a valid JSON Schema with required fields defined in properties. This ensures your tool definitions meet the 2024-11-05 specification for client compatibility.

You need MCP endpoint specification validation when implementing a new endpoint, modifying an existing handler, debugging client compatibility, or performing pre-release checks. This validation ensures your server conforms to the 2024-11-05 spec and JSON-RPC 2.0.

MCP client integration fails with JSON-RPC errors when response validation fails due to missing jsonrpc = '2.0', mismatched id, or improperly structured result or error fields. Validate your endpoint against the 2024-11-05 specification to resolve these compatibility issues.

Yes, you can use this validator to debug MCP endpoint compatibility across clients by enforcing that requests and responses adhere to the 2024-11-05 specification and JSON-RPC 2.0. It checks method and id presence, params schemas, and error code structures.