Remote MCP · Endpoint

Package Health Check MCP server

Yes, as of 4 hours ago: the server returned an HTTP error.

DownLast checked 4 hours ago

Server URL

https://packages.openkrill.app/mcp

The last check failed: the server returned an HTTP error.

Registry name
app.openkrill/packages
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Check an npm or Python package, or a package.json, for vulnerabilities and upkeep.
Listing
From the official MCP registry (active).
Recent checks of Package Health Check
CheckedResultHandshake
4 hours agoFailed - the server returned an HTTP error—
2 days agoHandshake completed145 ms
5 days agoHandshake completed293 ms
7 days agoHandshake completed186 ms
9 days agoHandshake completed152 ms
11 days agoHandshake completed175 ms
13 days agoHandshake completed1.42 s
15 days agoHandshake completed40 ms
17 days agoHandshake completed84 ms
18 days agoHandshake completed55 ms
20 days agoHandshake completed317 ms
21 days agoHandshake completed30 ms
23 days agoHandshake completed38 ms

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

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