MCP Endpoint Lint - handshake, tool schemas, JSON-RPC errors

Official registry Developer tools

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} free no key

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http mcp-endpoint-lint-handshake-tool-schemas 'https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/lint'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "mcp-endpoint-lint-handshake-tool-schemas": {
            "type": "http",
            "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/lint"
        }
    }
}

Frequently asked questions

What is MCP Endpoint Lint - handshake, tool schemas, JSON-RPC errors?

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} free no key

How do I install MCP Endpoint Lint - handshake, tool schemas, JSON-RPC errors?

It runs as a remote server. In Claude Code: claude mcp add --transport http mcp-endpoint-lint-handshake-tool-schemas 'https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/lint'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does MCP Endpoint Lint - handshake, tool schemas, JSON-RPC errors need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Who maintains MCP Endpoint Lint - handshake, tool schemas, JSON-RPC errors?

It is published by dev.workers.pathwren.www. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.