Remote MCP · Endpoint

Velven MCP server

No. Velven answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.velven.ai/mcp

The last check completed an MCP handshake.

Registry name
io.github.velvenai/velven
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
158 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 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
1 hour agoHandshake completed158 ms
2 days agoHandshake completed212 ms
4 days agoHandshake completed158 ms
6 days agoHandshake completed155 ms
8 days agoHandshake completed148 ms
10 days agoHandshake completed215 ms
12 days agoHandshake completed209 ms
14 days agoHandshake completed232 ms
15 days agoHandshake completed181 ms
16 days agoHandshake completed143 ms
17 days agoHandshake completed146 ms
20 days agoHandshake completed144 ms
22 days agoHandshake completed129 ms
23 days agoHandshake completed215 ms
25 days agoHandshake completed240 ms

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

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.