Remote MCP · Endpoint

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

No. MCP Endpoint Lint - handshake, tool schemas, JSON-RPC errors answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/lint

The last check completed an MCP handshake.

Registry name
dev.workers.pathwren.www/mcp-endpoint-lint
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
182 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} free no key
Listing
From the official MCP registry (active).
Recent checks of MCP Endpoint Lint - handshake, tool schemas, JSON-RPC errors
CheckedResultHandshake
1 hour agoHandshake completed182 ms
2 days agoHandshake completed182 ms
4 days agoHandshake completed246 ms
5 days agoHandshake completed147 ms
7 days agoHandshake completed91 ms
8 days agoHandshake completed544 ms
9 days agoHandshake completed180 ms
12 days agoHandshake completed50 ms
13 days agoHandshake completed200 ms
15 days agoHandshake completed145 ms
17 days agoHandshake completed229 ms
18 days agoHandshake completed22 ms
19 days agoHandshake completed194 ms
20 days agoHandshake completed209 ms
20 days agoHandshake completed155 ms
21 days agoHandshake completed19 ms
23 days agoHandshake completed68 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with MCP Endpoint Lint - handshake, tool schemas, JSON-RPC errors and makes no claim about it beyond what these checks measured.