Remote MCP · Endpoint

vrsai MCP server

No. vrsai answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.vrsai.tech/mcp

The last check completed an MCP handshake.

Registry name
tech.vrsai/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
682 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Machine-native capabilities with explicit contracts and machine-readable commerce.
Listing
From the official MCP registry (active).
Recent checks of vrsai
CheckedResultHandshake
1 hour agoHandshake completed682 ms
2 days agoHandshake completed377 ms
4 days agoHandshake completed578 ms
6 days agoHandshake completed62 ms
7 days agoHandshake completed475 ms
8 days agoHandshake completed546 ms
9 days agoHandshake completed706 ms
12 days agoHandshake completed430 ms
13 days agoHandshake completed464 ms
15 days agoHandshake completed412 ms
17 days agoHandshake completed86 ms
18 days agoHandshake completed351 ms
19 days agoHandshake completed375 ms
20 days agoHandshake completed462 ms
21 days agoHandshake completed324 ms
21 days agoHandshake completed426 ms
23 days agoHandshake completed516 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 vrsai and makes no claim about it beyond what these checks measured.