Remote MCP · Endpoint

RegiAI MCP server

No. RegiAI answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://regiai.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.regiai/regiai
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
407 ms
Tools exposed
51 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
AI image, video and audio tools: generate, edit, face swap, upscale, remove backgrounds, make video.
Listing
From the official MCP registry (active).
Recent checks of RegiAI
CheckedResultHandshake
2 hours agoHandshake completed407 ms
2 days agoHandshake completed396 ms
4 days agoHandshake completed415 ms
6 days agoHandshake completed381 ms
7 days agoHandshake completed722 ms
9 days agoHandshake completed406 ms
10 days agoHandshake completed404 ms
11 days agoHandshake completed480 ms
14 days agoHandshake completed380 ms
15 days agoHandshake completed373 ms
17 days agoHandshake completed390 ms
18 days agoHandshake completed387 ms
19 days agoHandshake completed394 ms
20 days agoHandshake completed396 ms
21 days agoHandshake completed432 ms
22 days agoHandshake completed409 ms
23 days agoHandshake completed460 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 RegiAI and makes no claim about it beyond what these checks measured.