Remote MCP · Endpoint

CareJobs.Now MCP server

No. CareJobs.Now answered an MCP handshake 15 minutes ago.

UpLast checked 15 minutes ago

Server URL

https://carejobs.now/api/mcp

The last check completed an MCP handshake.

Registry name
now.carejobs/healthcare-jobs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
74 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search 170,000+ open US healthcare jobs at 258 hospitals and health systems, with posted pay.
Listing
From the official MCP registry (active).
Recent checks of CareJobs.Now
CheckedResultHandshake
15 minutes agoHandshake completed74 ms
9 days agoHandshake completed397 ms
9 days agoHandshake completed455 ms
11 days agoHandshake completed296 ms
12 days agoHandshake completed135 ms
13 days agoHandshake completed59 ms
14 days agoHandshake completed291 ms
14 days agoHandshake completed146 ms
16 days agoHandshake completed177 ms
19 days agoHandshake completed137 ms
21 days agoHandshake completed58 ms
24 days agoHandshake completed85 ms
26 days agoHandshake completed91 ms
28 days agoHandshake completed121 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 CareJobs.Now and makes no claim about it beyond what these checks measured.