Remote MCP · Endpoint
workload.zero MCP server
No. workload.zero answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.workloadzero.de/mcp
The last check completed an MCP handshake.
- Registry name
- de.workloadzero/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 349 ms
- Tools exposed
- 151 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- Back office, projects, hiring and CRM in one suite. Claude's work stays a draft until you approve.
- Website
- https://workloadzero.de/en/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 349 ms |
| 12 hours ago | Handshake completed | 343 ms |
| 1 day ago | Credentials required | — |
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 workload.zero and makes no claim about it beyond what these checks measured.