Remote MCP · Endpoint

Depcheck MCP server

No. Depcheck answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://depcheck.kaneky.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.kaneky/depcheck
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
535 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Known vulnerabilities for exact package versions from OSV, with fixes. Paid per call, x402.
Listing
From the official MCP registry (active).
Recent checks of Depcheck
CheckedResultHandshake
1 hour agoHandshake completed535 ms
2 days agoHandshake completed417 ms
4 days agoHandshake completed400 ms
6 days agoHandshake completed456 ms
7 days agoHandshake completed408 ms
9 days agoHandshake completed436 ms
10 days agoHandshake completed455 ms
11 days agoHandshake completed404 ms
14 days agoHandshake completed397 ms
15 days agoHandshake completed418 ms
17 days agoHandshake completed439 ms
18 days agoHandshake completed398 ms
19 days agoHandshake completed394 ms
20 days agoHandshake completed401 ms
21 days agoHandshake completed406 ms
22 days agoHandshake completed408 ms

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

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 Depcheck and makes no claim about it beyond what these checks measured.