Remote MCP · Endpoint

io.github.theluckystrike/thumbnails MCP server

No. io.github.theluckystrike/thumbnails answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.zovo.one/mcp/thumbnails

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/thumbnails
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
149 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Generate image thumbnails, resize, convert and compress photos from your AI chat. Local files.
Listing
From the official MCP registry (active).
Recent checks of io.github.theluckystrike/thumbnails
CheckedResultHandshake
1 hour agoHandshake completed149 ms
3 days agoHandshake completed22 ms
12 days agoHandshake completed75 ms
13 days agoHandshake completed46 ms
15 days agoHandshake completed34 ms
15 days agoHandshake completed54 ms
17 days agoHandshake completed28 ms
18 days agoHandshake completed626 ms
18 days agoHandshake completed39 ms
20 days agoHandshake completed80 ms
23 days agoHandshake completed99 ms
25 days agoHandshake completed26 ms
28 days agoHandshake completed71 ms

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

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 io.github.theluckystrike/thumbnails and makes no claim about it beyond what these checks measured.