Remote MCP · Endpoint

DeAI Artifact Gateway MCP server

No. DeAI Artifact Gateway answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://research.zaiba.cloud/mcp

The last check completed an MCP handshake.

Registry name
io.github.jake-zaiba/deai-research
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
46 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Verified-artifact library: match, ask, run fixture programs, reuse sealed pages (HTTP 402 toll).
Listing
From the official MCP registry (active).
Recent checks of DeAI Artifact Gateway
CheckedResultHandshake
2 hours agoHandshake completed46 ms
1 day agoHandshake completed200 ms
2 days agoHandshake completed42 ms
3 days agoHandshake completed76 ms
4 days agoHandshake completed36 ms
5 days agoHandshake completed29 ms
7 days agoHandshake completed27 ms
9 days agoHandshake completed33 ms
12 days agoHandshake completed29 ms
14 days agoHandshake completed46 ms
16 days agoHandshake completed47 ms
18 days agoHandshake completed31 ms
20 days agoHandshake completed33 ms
22 days agoHandshake completed30 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 DeAI Artifact Gateway and makes no claim about it beyond what these checks measured.