Remote MCP · Endpoint
com.headcountdesk/site MCP server
No. com.headcountdesk/site answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://headcountdesk.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.headcountdesk/site
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 812 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- HeadcountDesk: the site's own MCP server — dataset; every answer cites the site.
- Website
- https://headcountdesk.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 812 ms |
| 18 hours ago | Handshake completed | 615 ms |
| 2 days ago | Handshake completed | 546 ms |
| 3 days ago | Handshake completed | 606 ms |
| 4 days ago | Handshake completed | 730 ms |
| 5 days ago | Handshake completed | 665 ms |
| 6 days ago | Handshake completed | 738 ms |
| 7 days ago | Handshake completed | 641 ms |
| 10 days ago | Handshake completed | 845 ms |
| 13 days ago | Handshake completed | 522 ms |
| 15 days ago | Handshake completed | 699 ms |
| 17 days ago | Handshake completed | 486 ms |
| 19 days ago | Handshake completed | 651 ms |
| 21 days ago | Handshake completed | 469 ms |
| 23 days ago | Handshake completed | 566 ms |
| 25 days ago | Handshake completed | 485 ms |
| 27 days ago | Handshake completed | 656 ms |
| 28 days ago | Handshake completed | 496 ms |
| 29 days ago | Handshake completed | 1.18 s |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 com.headcountdesk/site and makes no claim about it beyond what these checks measured.