Remote MCP · Endpoint

ViewMax MCP MCP server

No. ViewMax MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://viewmax.studio/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.bytevirts/viewmax
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
958 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Remote MCP for AI video, image, music and speech generation.
Listing
From the official MCP registry (active).
Recent checks of ViewMax MCP
CheckedResultHandshake
1 hour agoHandshake completed958 ms
2 days agoHandshake completed142 ms
4 days agoHandshake completed75 ms
5 days agoHandshake completed125 ms
7 days agoHandshake completed128 ms
8 days agoHandshake completed694 ms
9 days agoHandshake completed68 ms
12 days agoHandshake completed47 ms
13 days agoHandshake completed53 ms
15 days agoHandshake completed142 ms
16 days agoHandshake completed76 ms
18 days agoHandshake completed50 ms
19 days agoHandshake completed45 ms
20 days agoHandshake completed47 ms
20 days agoHandshake completed51 ms
21 days agoHandshake completed58 ms
22 days agoHandshake completed102 ms

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

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