Remote MCP · Endpoint

presign-guard MCP server

No. presign-guard answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://presign-guard.onrender.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.Fizzl13/presign-guard
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
137 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Pre-sign, token and approval checks for agents: green/orange/red for signatures, tokens, wallets.
Listing
From the official MCP registry (active).
Recent checks of presign-guard
CheckedResultHandshake
4 hours agoHandshake completed137 ms
2 days agoHandshake completed319 ms
4 days agoHandshake completed268 ms
6 days agoHandshake completed152 ms
7 days agoHandshake completed107 ms
9 days agoHandshake completed152 ms
10 days agoHandshake completed282 ms
11 days agoHandshake completed266 ms
14 days agoHandshake completed128 ms
15 days agoHandshake completed264 ms
17 days agoHandshake completed132 ms
19 days agoHandshake completed252 ms
20 days agoHandshake completed267 ms
21 days agoHandshake completed256 ms
22 days agoHandshake completed308 ms

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

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