Remote MCP · Endpoint

Velven MCP server

Yes, as of 8 hours ago: the server returned an HTTP error.

DownLast checked 8 hours ago

Server URL

https://mcp.velven.ai/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.velvenai/velven
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
5 tools
Uptime, last 30 days
71.4% from 14 checks
Described by its publisher as
Publish browser games, worlds, tools and wonders built with AI to Velven's hosting, and manage them.
Listing
From the official MCP registry (active).
Recent checks of Velven
CheckedResultHandshake
8 hours agoFailed - the server returned an HTTP error—
10 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
13 days agoHandshake completed151 ms
15 days agoHandshake completed141 ms
15 days agoHandshake completed152 ms
16 days agoHandshake completed196 ms
17 days agoHandshake completed166 ms
19 days agoHandshake completed226 ms
22 days agoHandshake completed216 ms
24 days agoHandshake completed158 ms
26 days agoHandshake completed212 ms
29 days agoHandshake completed158 ms

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

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