Remote MCP · Endpoint

JPG.now MCP Server MCP server

No. JPG.now MCP Server answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://jpg.now/mcp

The last check completed an MCP handshake.

Registry name
io.github.chrisyau83/jpg-now
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
142 ms
Tools exposed
4 tools
Uptime, last 30 days
81.8% from 11 checks
Described by its publisher as
Convert JPG images to and from popular formats through MCP-compatible AI clients.
Listing
From the official MCP registry (active).
Recent checks of JPG.now MCP Server
CheckedResultHandshake
35 minutes agoHandshake completed142 ms
3 days agoHandshake completed94 ms
13 days agoHandshake completed185 ms
13 days agoHandshake completed81 ms
15 days agoHandshake completed91 ms
16 days agoHandshake completed124 ms
17 days agoHandshake completed127 ms
18 days agoHandshake completed125 ms
18 days agoFailed - the request timed out—
20 days agoHandshake completed82 ms
22 days agoFailed - the request timed out—

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

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