CuratorSearch MCP server
Which servers in the official MCP registry are CuratorSearch's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-19
- Registry namecom.curatorsearch/jobsverified in the MCP registry
The registry name sits under curatorsearch.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-19
- Tools4
- Server calls itselfcuratorsearch
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 178 ms.
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer224 ms
- Space in an agent's context≈ 515 tokensthe definitions of all its tools (4), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Every tool passes all six checks.
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work.
search_jobsSearch live museum, gallery and curatorial job listings, gathered daily from institutions' own career pages. Returns up to 20 roles, newest first, each with its curatorsearch.com page.
get_jobOne listing in full: description, stated salary, deadline, and the institution's original posting URL. Takes the slug from a curatorsearch.com/opportunities/<slug> URL.
institution_jobsEvery role one museum or gallery currently has open on the board, by institution name.
salary_transparencyHow many live museum and curatorial postings state a salary, and the median advertised figure among those that do -- the CuratorSearch Curatorial Pay Archive headline number, computed live.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"jobs": {
"type": "http",
"url": "https://curatorsearch.com/mcp"
}
}
}OpenAPI spec
3 paths, read 2026-10-19. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.