Remote MCP · Endpoint

JobsRadar MCP server

No. JobsRadar answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
787 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
1 hour agoHandshake completed787 ms
2 days agoHandshake completed674 ms
4 days agoHandshake completed692 ms
6 days agoHandshake completed553 ms
8 days agoHandshake completed1.19 s
10 days agoHandshake completed634 ms
12 days agoHandshake completed600 ms
14 days agoHandshake completed533 ms
16 days agoHandshake completed644 ms
17 days agoHandshake completed410 ms
18 days agoHandshake completed704 ms
20 days agoHandshake completed553 ms
22 days agoHandshake completed582 ms
24 days agoCredentials required—

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

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.