Remote MCP · Endpoint

JobsRadar MCP server

No. JobsRadar answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://jobsradar.agenttoolworks.com/mcp

The last check completed an MCP handshake.

Registry name
com.agenttoolworks/jobsradar
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
538 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Job search across Greenhouse, Lever, Ashby, SmartRecruiters, Personio and Pinpoint, deduplicated.
Listing
From the official MCP registry (active).
Recent checks of JobsRadar
CheckedResultHandshake
5 hours agoHandshake completed538 ms
9 days agoHandshake completed496 ms
10 days agoHandshake completed714 ms
11 days agoHandshake completed539 ms
12 days agoHandshake completed515 ms
14 days agoHandshake completed1.50 s
14 days agoHandshake completed376 ms
15 days agoHandshake completed712 ms
17 days agoHandshake completed750 ms
19 days agoHandshake completed517 ms
21 days agoHandshake completed787 ms
24 days agoHandshake completed674 ms
26 days agoHandshake completed692 ms
28 days agoHandshake completed553 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 24 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 JobsRadar and makes no claim about it beyond what these checks measured.