Remote MCP · Endpoint

SafeResize MCP server

No. SafeResize answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://saferesize.com/mcp

The last check completed an MCP handshake.

Registry name
com.saferesize/saferesize
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
451 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Passport and visa photo rules for 110 documents in 60 countries, and upload limits as exact numbers.
Listing
From the official MCP registry (active).
Recent checks of SafeResize
CheckedResultHandshake
1 hour agoHandshake completed451 ms
2 days agoHandshake completed77 ms
4 days agoHandshake completed70 ms
6 days agoHandshake completed63 ms
8 days agoHandshake completed74 ms
10 days agoHandshake completed68 ms
12 days agoHandshake completed92 ms
14 days agoHandshake completed71 ms
15 days agoHandshake completed92 ms
16 days agoHandshake completed308 ms
18 days agoHandshake completed102 ms
20 days agoHandshake completed75 ms
22 days agoHandshake completed77 ms
24 days agoHandshake completed105 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 SafeResize and makes no claim about it beyond what these checks measured.