Remote MCP · Endpoint

Foca Upscaler MCP server

No. Foca Upscaler answered an MCP handshake 16 minutes ago.

UpLast checked 16 minutes ago

Server URL

https://focaupscaler.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.focaupscaler/upscaler
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
501 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Upscale images from HTTPS URLs with account credits and retrieve async results.
Listing
From the official MCP registry (active).
Recent checks of Foca Upscaler
CheckedResultHandshake
16 minutes agoHandshake completed501 ms
9 days agoHandshake completed609 ms
9 days agoHandshake completed606 ms
11 days agoHandshake completed767 ms
12 days agoHandshake completed661 ms
13 days agoHandshake completed792 ms
14 days agoHandshake completed569 ms
14 days agoHandshake completed557 ms
16 days agoHandshake completed925 ms
19 days agoHandshake completed746 ms
21 days agoHandshake completed946 ms
24 days agoHandshake completed1.29 s
26 days agoHandshake completed644 ms
28 days agoHandshake completed773 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 Foca Upscaler and makes no claim about it beyond what these checks measured.