Remote MCP · Endpoint

Presend dependency checks MCP server

No. Presend dependency checks answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://presend.pages.dev/mcp-deps

The last check completed an MCP handshake.

Registry name
io.github.presendapp/presend-deps
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
168 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Check an npm/PyPI package before an AI agent installs it: 5 focused supply-chain tools.
Listing
From the official MCP registry (active).
Recent checks of Presend dependency checks
CheckedResultHandshake
7 hours agoHandshake completed168 ms
2 days agoHandshake completed149 ms
5 days agoHandshake completed147 ms
7 days agoHandshake completed140 ms
9 days agoHandshake completed232 ms
11 days agoHandshake completed229 ms
13 days agoHandshake completed68 ms
15 days agoHandshake completed126 ms
17 days agoHandshake completed173 ms
19 days agoHandshake completed54 ms
20 days agoHandshake completed34 ms
21 days agoHandshake completed125 ms
23 days agoHandshake completed135 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 Presend dependency checks and makes no claim about it beyond what these checks measured.