Remote MCP · Endpoint

Vi Assistant by Vultax MCP server

No. Vi Assistant by Vultax answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://vultax.com/vi-mcp

The last check completed an MCP handshake.

Registry name
io.github.Vultax/vultax-research
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
344 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Vi market evidence, hypothetical price scenarios and published Vultax research.
Listing
From the official MCP registry (active).
Recent checks of Vi Assistant by Vultax
CheckedResultHandshake
1 day agoHandshake completed344 ms
2 days agoHandshake completed316 ms
5 days agoHandshake completed327 ms
7 days agoHandshake completed328 ms
9 days agoHandshake completed303 ms
10 days agoHandshake completed306 ms
12 days agoHandshake completed352 ms
13 days agoHandshake completed303 ms
14 days agoHandshake completed415 ms
17 days agoHandshake completed361 ms
18 days agoHandshake completed355 ms
20 days agoHandshake completed343 ms
21 days agoHandshake completed373 ms
22 days agoHandshake completed366 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 Vi Assistant by Vultax and makes no claim about it beyond what these checks measured.