Remote MCP · Endpoint

ImgVX AI MCP server

No. ImgVX AI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://imgvx.com/mcp

The last check completed an MCP handshake.

Registry name
com.imgvx/imgvx-ai
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
123 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find the free ImgVX AI browser tool for any image job: remove backgrounds, upscale, compress.
Listing
From the official MCP registry (active).
Recent checks of ImgVX AI
CheckedResultHandshake
1 hour agoHandshake completed123 ms
19 hours agoHandshake completed91 ms
1 day agoHandshake completed98 ms
2 days agoHandshake completed120 ms
4 days agoHandshake completed418 ms
7 days agoHandshake completed71 ms
9 days agoHandshake completed635 ms
12 days agoHandshake completed165 ms
14 days agoHandshake completed147 ms
16 days agoHandshake completed144 ms
18 days agoHandshake completed107 ms
20 days agoHandshake completed174 ms
22 days agoHandshake completed107 ms
23 days agoHandshake completed116 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 ImgVX AI and makes no claim about it beyond what these checks measured.