Remote MCP · Endpoint

Shotkiln MCP server

No. Shotkiln answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://shotkiln.com/mcp

The last check completed an MCP handshake.

Registry name
com.shotkiln/shotkiln
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
149 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Screenshot, PDF and Open Graph image API for AI agents: capture pages, render PDFs, make OG images.
Listing
From the official MCP registry (active).
Recent checks of Shotkiln
CheckedResultHandshake
18 minutes agoHandshake completed149 ms
9 days agoHandshake completed132 ms
9 days agoHandshake completed161 ms
11 days agoHandshake completed49 ms
12 days agoHandshake completed151 ms
13 days agoHandshake completed154 ms
14 days agoHandshake completed118 ms
14 days agoHandshake completed112 ms
16 days agoHandshake completed125 ms
19 days agoHandshake completed286 ms
21 days agoHandshake completed289 ms
24 days agoHandshake completed166 ms
26 days agoHandshake completed111 ms

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

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