Remote MCP · Endpoint
Vetofix – Hilfe zur Praxissoftware für Tierarzt-Hausbesuche MCP server
No. Vetofix – Hilfe zur Praxissoftware für Tierarzt-Hausbesuche answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://vetofix.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.vetofix/hilfe
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 308 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- Help and FAQ for Vetofix, practice software for mobile veterinarians. Read-only, no patient data.
- Website
- https://vetofix.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 308 ms |
| 1 day ago | Handshake completed | 328 ms |
| 2 days ago | Handshake completed | 320 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.
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 Vetofix – Hilfe zur Praxissoftware für Tierarzt-Hausbesuche and makes no claim about it beyond what these checks measured.