Remote MCP · Endpoint

presign-guard MCP server

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

UpLast checked 6 hours ago

Server URL

https://presign-guard.fizzl.eu/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
134 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Safe to sign? EVM/Solana/XRPL/Algorand txs, permits, EIP-7702, tokens; OFAC screen: green/orange/red
Listing
From the official MCP registry (active).
Recent checks of presign-guard
CheckedResultHandshake
6 hours agoHandshake completed134 ms
2 days agoHandshake completed153 ms
4 days agoHandshake completed264 ms
6 days agoHandshake completed145 ms
8 days agoHandshake completed171 ms
10 days agoHandshake completed124 ms
12 days agoHandshake completed131 ms
13 days agoHandshake completed142 ms
14 days agoHandshake completed277 ms
15 days agoHandshake completed296 ms
18 days agoHandshake completed188 ms
20 days agoHandshake completed278 ms
21 days agoHandshake completed273 ms
22 days agoHandshake completed328 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 presign-guard and makes no claim about it beyond what these checks measured.