Remote MCP · Endpoint

FrameAnyPhoto MCP server

No. FrameAnyPhoto answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://frameanyphoto.com/mcp

The last check completed an MCP handshake.

Registry name
com.frameanyphoto/prints
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
423 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Shop for and buy framed museum-quality prints of public-domain art and photos, shipped US-wide.
Listing
From the official MCP registry (active).
Recent checks of FrameAnyPhoto
CheckedResultHandshake
1 hour agoHandshake completed423 ms
17 hours agoHandshake completed140 ms
1 day agoHandshake completed239 ms
3 days agoHandshake completed404 ms
5 days agoHandshake completed276 ms
7 days agoHandshake completed237 ms
10 days agoHandshake completed294 ms
12 days agoHandshake completed275 ms
14 days agoHandshake completed250 ms
16 days agoHandshake completed254 ms
18 days agoHandshake completed325 ms
20 days agoHandshake completed267 ms
22 days agoHandshake completed241 ms
23 days agoHandshake completed243 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 FrameAnyPhoto and makes no claim about it beyond what these checks measured.