Remote MCP · Endpoint

Presend dependency checks MCP server

No. Presend dependency checks answered an MCP handshake 46 minutes ago.

UpLast checked 46 minutes 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
196 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
46 minutes agoHandshake completed196 ms
3 days agoHandshake completed130 ms
13 days agoHandshake completed277 ms
13 days agoHandshake completed186 ms
15 days agoHandshake completed194 ms
16 days agoHandshake completed301 ms
17 days agoHandshake completed158 ms
18 days agoHandshake completed167 ms
18 days agoHandshake completed142 ms
20 days agoHandshake completed337 ms
22 days agoHandshake completed168 ms
25 days agoHandshake completed149 ms
27 days agoHandshake completed147 ms
30 days agoHandshake completed140 ms

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

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.