Remote MCP · Endpoint

VegvisAI guide MCP server

No. VegvisAI guide answered an MCP handshake 46 minutes ago.

UpLast checked 46 minutes ago

Server URL

https://vegvis.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.vegvis/vegvisai
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
128 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Open guide to businesses in any country, plus Norwegian public services and parties. Never ranks.
Listing
From the official MCP registry (active).
Recent checks of VegvisAI guide
CheckedResultHandshake
46 minutes agoHandshake completed128 ms
3 days agoHandshake completed87 ms
13 days agoHandshake completed150 ms
13 days agoHandshake completed153 ms
15 days agoHandshake completed92 ms
16 days agoHandshake completed111 ms
17 days agoHandshake completed103 ms
18 days agoHandshake completed117 ms
18 days agoHandshake completed114 ms
20 days agoHandshake completed194 ms
22 days agoHandshake completed113 ms
25 days agoHandshake completed242 ms
27 days agoHandshake completed118 ms
30 days agoHandshake completed50 ms

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

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