Remote MCP · Endpoint

DepScout MCP server

No. DepScout answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://depscout.salesup.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.yc-droid/depscout
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
185 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Scan packages and lockfiles (npm, PyPI, Go, Maven, Cargo, NuGet) for vulnerabilities and malware.
Listing
From the official MCP registry (active).
Recent checks of DepScout
CheckedResultHandshake
1 hour agoHandshake completed185 ms
20 hours agoHandshake completed232 ms
2 days agoHandshake completed581 ms
4 days agoHandshake completed293 ms
6 days agoHandshake completed260 ms
9 days agoHandshake completed180 ms
11 days agoHandshake completed246 ms
13 days agoHandshake completed233 ms
15 days agoHandshake completed272 ms
17 days agoHandshake completed152 ms
19 days agoHandshake completed300 ms
21 days agoHandshake completed228 ms
23 days agoHandshake completed292 ms
24 days agoHandshake completed207 ms

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

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