Remote MCP · Endpoint

VegvisAI guide MCP server

No. VegvisAI guide answered an MCP handshake 5 hours ago.

UpLast checked 5 hours 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
113 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
5 hours agoHandshake completed113 ms
2 days agoHandshake completed242 ms
5 days agoHandshake completed118 ms
7 days agoHandshake completed50 ms
9 days agoHandshake completed97 ms
11 days agoHandshake completed180 ms
13 days agoHandshake completed117 ms
15 days agoHandshake completed102 ms
17 days agoHandshake completed80 ms
18 days agoHandshake completed136 ms
20 days agoHandshake completed135 ms
21 days agoHandshake completed81 ms
23 days agoHandshake completed125 ms

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

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.