Reviews
No review yet. Used MCP Endpoint Lint - handshake, tool schemas, JSON-RPC errors? Be the first to help others choose.What it does
MCP Endpoint Lint - handshake, tool schemas, JSON-RPC errors is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 16h ago (live check)Hosted endpoint
https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/lintstreamable-http
In Claude Code: claude mcp add --transport http mcp-endpoint-lint-handshake-tool-schemas-json-rpc-errors https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/lint
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"mcp-endpoint-lint-handshake-tool-schemas-json-rpc-errors": {
"url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/lint"
}
}
}Live check
Electra Index connected to the hosted endpoint 16h agoONLINE MCP Endpoint Lint - handshake, tool schemas, JSON-RPC errors answered an MCP connection on 17 Nov 2026 and introduced itself as mcp-endpoint-lint 1.0.0 (MCP protocol 2025-06-18).
7 tools offered to AI assistants
whoami· {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} — POST that to https://www.pathwren.workers.dev/mcp/lint and the answer is the user-agent you sent, the class this host's own instrument books it as, wexample· {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"example","arguments":{}}} — POST that exact body to https://www.pathwren.workers.dev/mcp/lint and you are done: free, read-only, no API key, no account, no consent prompt, nothhandshake_report· FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} — POST initialize to an MCP endpoint you name and report what came back: the protocol version it negotiated against the onetools_list_report· FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} — Handshake, then tools/list, then check every tool it returns: a missing or empty description, a description too short to cerror_conformance· FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} — Send five things a real client eventually sends by accident and check what comes back: an unknown method (expects -32601),discovery_report· FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} — GET the documents an MCP client reads BEFORE the handshake and report what each one answered: /.well-known/oauth-protectedscore_card· FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} — Run handshake_report, tools_list_report, error_conformance and discovery_report against one endpoint and return a single v
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/lint | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Website | https://www.pathwren.workers.dev/c/mcp-registry-official/mcp-lint.html | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Version | 1.3.0 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is MCP Endpoint Lint - handshake, tool schemas, JSON-RPC errors still online?
Free alerts · no account▲ 0Do you run MCP Endpoint Lint - handshake, tool schemas, JSON-RPC errors? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about MCP Endpoint Lint - handshake, tool schemas, JSON-RPC errors
How do I connect MCP Endpoint Lint - handshake, tool schemas, JSON-RPC errors?
Use the hosted endpoint https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/lint in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does MCP Endpoint Lint - handshake, tool schemas, JSON-RPC errors offer?
When Electra Index connected on 17 Nov 2026, it listed 7 tools: whoami, example, handshake_report, tools_list_report, error_conformance, discovery_report, score_card. The full list is in "Live check" above.
Is MCP Endpoint Lint - handshake, tool schemas, JSON-RPC errors online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 16h ago.