Remote MCP · Endpoint
Was ist MCP? Demo-Server MCP server
No. Was ist MCP? Demo-Server answered an MCP handshake 9 hours ago.
UpLast checked 9 hours ago
Server URL
https://mcp.was-ist-mcp.ch/mcp
The last check completed an MCP handshake.
- Registry name
- ch.was-ist-mcp/demo
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 335 ms
- Tools exposed
- 10 tools
- Uptime, last 30 days
- 81.8% from 11 checks
- Described by its publisher as
- Plain-language MCP explainer in German: search and read was-ist-mcp.ch. Most tools need no login.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 9 hours ago | Handshake completed | 335 ms |
| 4 days ago | Handshake completed | 370 ms |
| 14 days ago | Failed - the request timed out | — |
| 15 days ago | Handshake completed | 326 ms |
| 15 days ago | Handshake completed | 342 ms |
| 17 days ago | Handshake completed | 321 ms |
| 18 days ago | Handshake completed | 317 ms |
| 19 days ago | Handshake completed | 329 ms |
| 20 days ago | Handshake completed | 321 ms |
| 21 days ago | Failed - the request timed out | — |
| 23 days ago | Handshake completed | 323 ms |
The last 11 checks. Full history is kept for 30 days; the all-time counter stands at 9 responding of 11.
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 Was ist MCP? Demo-Server and makes no claim about it beyond what these checks measured.