Remote MCP · Endpoint

Vizier MCP server

No. Vizier answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://vizier.agendamcp.dpdns.org/mcp

The last check completed an MCP handshake.

Registry name
io.github.vassiliylakhonin/vizier
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
254 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Owner-signed permissions for AI agent actions; ALLOW/BLOCK/REVIEW with request-bound receipts.
Listing
From the official MCP registry (active).
Recent checks of Vizier
CheckedResultHandshake
2 hours agoHandshake completed254 ms
1 day agoHandshake completed314 ms
2 days agoHandshake completed242 ms
3 days agoHandshake completed157 ms
4 days agoHandshake completed243 ms
5 days agoHandshake completed218 ms
6 days agoHandshake completed317 ms
8 days agoHandshake completed211 ms
11 days agoHandshake completed356 ms
13 days agoHandshake completed193 ms
15 days agoHandshake completed234 ms
18 days agoHandshake completed297 ms
20 days agoHandshake completed271 ms
22 days agoHandshake completed327 ms
24 days agoHandshake completed181 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 Vizier and makes no claim about it beyond what these checks measured.