Remote MCP · Endpoint

freehire MCP server

No. freehire answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://freehire.me/api/v1/mcp

The last check completed an MCP handshake.

Registry name
me.freehire/freehire
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
157 ms
Tools exposed
38 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
freehire.me: search 3.3M+ IT jobs from 294K company boards, track applications, tailor CVs.
Listing
From the official MCP registry (active).
Recent checks of freehire
CheckedResultHandshake
2 days agoHandshake completed157 ms
3 days agoHandshake completed215 ms
3 days agoHandshake completed383 ms
5 days agoHandshake completed165 ms
6 days agoHandshake completed188 ms
7 days agoHandshake completed141 ms
8 days agoHandshake completed156 ms
9 days agoHandshake completed449 ms
11 days agoHandshake completed420 ms
13 days agoHandshake completed385 ms
16 days agoHandshake completed173 ms
18 days agoHandshake completed162 ms
21 days agoHandshake completed178 ms
22 days agoHandshake completed277 ms
25 days agoHandshake completed474 ms

The last 15 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 freehire and makes no claim about it beyond what these checks measured.