Remote MCP · Endpoint

Headcount Labs MCP server

No. Headcount Labs answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.headcountlabs.com/mcp/public

The last check completed an MCP handshake.

Registry name
com.headcountlabs/jobs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
373 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Job postings search: find, count and read open jobs from employer career sites, with pay and links.
Listing
From the official MCP registry (active).
Recent checks of Headcount Labs
CheckedResultHandshake
1 hour agoHandshake completed373 ms
8 days agoHandshake completed429 ms
9 days agoHandshake completed175 ms
11 days agoHandshake completed392 ms
12 days agoHandshake completed378 ms
12 days agoHandshake completed499 ms
14 days agoHandshake completed158 ms
14 days agoHandshake completed518 ms
16 days agoHandshake completed308 ms
19 days agoHandshake completed482 ms
21 days agoHandshake completed509 ms
24 days agoHandshake completed567 ms
26 days agoHandshake completed165 ms
28 days agoHandshake completed305 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

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 Headcount Labs and makes no claim about it beyond what these checks measured.