MCP Endpoint Lint - handshake, tool schemas, JSON-RPC errors
by pathwren.workers.dev in Onchain & crypto
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} free no key
https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/lint- Tools
- 7
- open to any client
- Uptime
- 94.1%
- last 30 days
- Response time
- 229 ms
- 387 ms slowest 5%
- Last check
- Passed
- 9 h ago, next any minute now
This listing's own text contains instructions aimed at AI agents (see the security scan below). We withhold that text from agents and never recommend this service.
Reliability
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"mcp-endpoint-lint-handshake-tool-schemas-json-rpc-errors": {
"type": "http",
"url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/lint"
}
}
}7 tools
- 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, whether we have logged you here before…
- example
{"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, nothing for you to invent, and what comes…
- handshake_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 one you asked for, the capabilities it…
- tools_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 choose on, a missing inputSchema, an…
- error_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), tools/call naming a tool that does not…
- 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-protected-resource in BOTH forms — the root form…
- score_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 verdict: a score out of 100 (handshake…
Security scan
1 finding
- Mentions credentials or secret files in tool:discovery_report
n-server, /.well-known/mcp, /.well-known/mcp.json, /mcp.json and /llms.txt. Each result carries the status, the verdict (served, missing, ga
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 9 h ago | Passed | 200 | 235 ms |
| 19 h ago | Passed | 200 | 387 ms |
| 30 h ago | Passed | 200 | 270 ms |
| 40 h ago | Passed | 200 | 241 ms |
| 2 days ago | Passed | 200 | 220 ms |
Show 10 older checks
| 3 days ago | Passed | 200 | 229 ms |
| 3 days ago | Passed | 200 | 225 ms |
| 3 days ago | Timed out | - | - |
| 4 days ago | Passed | 200 | 381 ms |
| 4 days ago | Passed | 200 | 256 ms |
| 5 days ago | Passed | 200 | 206 ms |
| 5 days ago | Passed | 200 | 158 ms |
| 5 days ago | Passed | 200 | 222 ms |
| 6 days ago | Passed | 200 | 281 ms |
| 6 days ago | Passed | 200 | 251 ms |