Remote MCP · Endpoint
CuratorSearch MCP server
No. CuratorSearch answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://curatorsearch.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.curatorsearch/jobs
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 111 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Live museum and curatorial job listings from institutions' own careers pages, plus a salary archive.
- Website
- https://curatorsearch.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 111 ms |
| 19 hours ago | Handshake completed | 125 ms |
| 2 days ago | Handshake completed | 129 ms |
| 3 days ago | Handshake completed | 121 ms |
| 4 days ago | Handshake completed | 113 ms |
| 5 days ago | Handshake completed | 115 ms |
| 6 days ago | Handshake completed | 140 ms |
| 8 days ago | Handshake completed | 122 ms |
| 10 days ago | Handshake completed | 114 ms |
| 13 days ago | Handshake completed | 111 ms |
| 15 days ago | Handshake completed | 116 ms |
| 17 days ago | Handshake completed | 119 ms |
| 19 days ago | Handshake completed | 110 ms |
| 21 days ago | Handshake completed | 108 ms |
| 23 days ago | Handshake completed | 116 ms |
| 25 days ago | Handshake completed | 122 ms |
| 27 days ago | Handshake completed | 142 ms |
| 28 days ago | Handshake completed | 134 ms |
| 29 days ago | Handshake completed | 118 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 CuratorSearch and makes no claim about it beyond what these checks measured.