Remote MCP · Endpoint

Cerulean Jobs MCP server

No. Cerulean Jobs answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ceruleanjobs.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.ceruleanjobs/search
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
173 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Open jobs at luxury houses and brands worldwide: search them, read one in full, find roles like it.
Listing
From the official MCP registry (active).
Recent checks of Cerulean Jobs
CheckedResultHandshake
1 hour agoHandshake completed173 ms
2 days agoHandshake completed64 ms
4 days agoHandshake completed82 ms
6 days agoHandshake completed142 ms
7 days agoHandshake completed104 ms
9 days agoHandshake completed100 ms
10 days agoHandshake completed78 ms
11 days agoHandshake completed83 ms
14 days agoHandshake completed68 ms
15 days agoHandshake completed93 ms
17 days agoHandshake completed97 ms
18 days agoHandshake completed99 ms
19 days agoHandshake completed89 ms
21 days agoHandshake completed78 ms
22 days agoHandshake completed91 ms
22 days agoHandshake completed132 ms

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

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