Remote MCP · Endpoint
HireHeat MCP server
Yes, as of 2 hours ago: the check failed for an unclassified reason.
DownLast checked 2 hours ago
Server URL
https://hireheat-api.cybermax-tools.workers.dev/mcp?via=mcp-registry
The last check failed: the check failed for an unclassified reason.
- Registry name
- dev.workers.cybermax-tools.cybermax/hireheat-api
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 85.7% from 14 checks
- Described by its publisher as
- Company hiring signals + open jobs from Greenhouse, Lever, Ashby boards, API + MCP. 20 free/day.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Failed - the check failed for an unclassified reason | — |
| 10 days ago | Handshake completed | 97 ms |
| 11 days ago | Handshake completed | 260 ms |
| 11 days ago | Handshake completed | 560 ms |
| 13 days ago | Handshake completed | 91 ms |
| 14 days ago | Handshake completed | 94 ms |
| 15 days ago | Handshake completed | 236 ms |
| 16 days ago | Handshake completed | 379 ms |
| 17 days ago | Handshake completed | 104 ms |
| 19 days ago | Handshake completed | 369 ms |
| 22 days ago | Handshake completed | 112 ms |
| 24 days ago | Handshake completed | 177 ms |
| 26 days ago | Handshake completed | 105 ms |
| 29 days ago | Failed - the check failed for an unclassified reason | — |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 21 responding of 24.
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 HireHeat and makes no claim about it beyond what these checks measured.