Remote MCP · Endpoint

vidit (demo) MCP server

No. vidit (demo) answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://mcp.vidit.ch/mcp/r

The last check completed an MCP handshake.

Registry name
ch.vidit/demo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
437 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Demo of a Swiss tax service for AI agents: AI-drafted answers, sample quotes, nothing validated yet.
Listing
From the official MCP registry (active).
Recent checks of vidit (demo)
CheckedResultHandshake
34 minutes agoHandshake completed437 ms
9 days agoHandshake completed315 ms
10 days agoHandshake completed284 ms
11 days agoHandshake completed332 ms
12 days agoHandshake completed337 ms
14 days agoHandshake completed304 ms
14 days agoHandshake completed277 ms
15 days agoHandshake completed283 ms
17 days agoHandshake completed283 ms
19 days agoHandshake completed322 ms
21 days agoHandshake completed315 ms
24 days agoHandshake completed307 ms
26 days agoHandshake completed411 ms
28 days agoHandshake completed291 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 vidit (demo) and makes no claim about it beyond what these checks measured.