Remote MCP · Endpoint

PkgGuard MCP server

No. PkgGuard answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://api.youraitools.co/pkgguard/mcp

The last check completed an MCP handshake.

Registry name
co.youraitools/pkgguard
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
238 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Dependency scan for agents: known CVEs and malicious packages via OSV.dev. By Crypto Money Maker
Listing
From the official MCP registry (active).
Recent checks of PkgGuard
CheckedResultHandshake
56 minutes agoHandshake completed238 ms
3 days agoHandshake completed566 ms
12 days agoHandshake completed88 ms
13 days agoHandshake completed231 ms
15 days agoHandshake completed232 ms
15 days agoHandshake completed39 ms
17 days agoHandshake completed318 ms
18 days agoHandshake completed36 ms
18 days agoHandshake completed265 ms
20 days agoHandshake completed297 ms
22 days agoHandshake completed111 ms
25 days agoHandshake completed279 ms
27 days agoHandshake completed177 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 PkgGuard and makes no claim about it beyond what these checks measured.