CuratorSearch
REMOTE · CURATORSEARCH.COM
Live museum and curatorial job listings from institutions' own careers pages, plus a salary archive.
Available components
Last scanned (7 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 358 tokens (~89/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 7 Nov 26 +1
- Stability: 0.97 → pass security
- Endpoint reachability: unreachable → reachable ▲ functional
- 6 Nov 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 8 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Sept 26 0
- Authorization: unverified → partial ▲ security
- Schema quality: 68 → 89 ▼ functional
- Tool coverage: 17% → 100% ▲ functional
- Tool “get_job” now declares an output schema ▲ functional
- Tool “institution_jobs” now declares an output schema ▲ functional
- Tool “salary_transparency” now declares an output schema ▲ functional
- Tool “search_jobs” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: good → excellent functional
- “get_job” reworded the description of “slug” cosmetic
- “institution_jobs” reworded the description of “institution” cosmetic
- “search_jobs” reworded the description of “category” cosmetic
- “search_jobs” reworded the description of “limit” cosmetic
- “search_jobs” reworded the description of “query” cosmetic
- “search_jobs” reworded the description of “region” cosmetic
- 8 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Nov 2026 · Probed https://curatorsearch.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=curatorsearch.com | CN=YR1,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | RSA 2048 | SHA256-RSA | 519a0faa15a17f3f80cbbe2b74d8a4da237 |
| SANs: curatorsearch.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of curatorsearch.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| curatorsearch.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://curatorsearch.com/mcp | Verified | 200 | |
| http (plaintext) | http://curatorsearch.com/mcp | HTTPS enforced | 301 | https://curatorsearch.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_job ~71
One listing in full: description, stated salary, deadline, and the institution's original posting URL. Takes the slug from a curatorsearch.com/opportunities/<slug> URL.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The listing's slug, or the whole curatorsearch.com/opportunities/<slug> URL -- either is accepted. |
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | CuratorSearch field, one of the category values. |
| deadline | string|null | – | Application deadline as an ISO date, or null if none is given. |
| description | string|null | – | The posting's own text, or null if the source gave none. |
| institution | string | yes | Museum, gallery or organisation advertising the role. |
| location | string|null | – | City and country as stated, or null if the posting gives none. |
| posted | string | yes | ISO date the role was first seen on the board. |
| region | string | yes | CuratorSearch world region. |
| salary | string|null | – | Pay exactly as the posting states it, or null -- most postings state none. |
| source | string | yes | The institution's original posting, where applications are made. |
| status | string | yes | 'live' while the role is open; anything else means the institution has taken it down. |
| title | string | yes | Job title as advertised. |
| url | string | yes | The role's permanent page on curatorsearch.com. |
No examples provided.
institution_jobs ~59
Every role one museum or gallery currently has open on the board, by institution name.
| Name | Type | Req | Description |
|---|---|---|---|
| institution | string | yes | The institution's name, e.g. 'Philadelphia Museum of Art'. Near-misses resolve; if nothing matches, the reply says so. |
| Name | Type | Req | Description |
|---|---|---|---|
| institution | string | yes | The institution as the board names it. |
| note | string | – | Present only when no institution of that name is on the board. |
| page | string | – | That institution's page on curatorsearch.com. |
| results | array | yes | Its open roles, newest first. |
No examples provided.
salary_transparency ~45
How 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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | – | ISO date the figures were computed. |
| citation | string | – | How to cite these figures. |
| liveListings | integer | – | Live roles on the board at the moment of the call. |
| medianAdvertisedEurPerYear | integer | – | Median stated figure among those that do, annualised into euro. |
| note | string | – | Present only when there is no salary data yet. |
| percentStatingSalary | number | – | Percentage of those postings that state any pay at all. |
No examples provided.
search_jobs ~126
Search 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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Restrict to one field of work. |
| limit | integer | – | How many roles to return, 1 to 20. Defaults to 10. |
| query | string | – | Free text matched against title, institution and location, e.g. 'registrar London'. Omit to browse everything. |
| region | string | – | Restrict to one world region. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | Source credit to quote when citing these results. |
| results | array | yes | The matching roles, newest first. |
| total | integer | yes | How many live roles match, which may exceed the number returned. |
No examples provided.
How do I install the CuratorSearch MCP server?
CuratorSearch is a hosted endpoint at https://curatorsearch.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · curatorsearch.com
claude mcp add --transport http com-curatorsearch-jobs 'https://curatorsearch.com/mcp'
What is the CuratorSearch MCP server?
CuratorSearch is an MCP server listed in the public MCP registry as com.curatorsearch/jobs. Live museum and curatorial job listings from institutions' own careers pages, plus a salary archive. This page covers its hosted endpoint (https://curatorsearch.com/mcp).
Is the CuratorSearch MCP server safe to use?
CuratorSearch scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CuratorSearch MCP server expose?
CuratorSearch exposes 4 tools: search_jobs, get_job, institution_jobs, salary_transparency. Their descriptions and schemas cost roughly 301 tokens of context every time the server is loaded.
Does the CuratorSearch MCP server require authentication?
No. We connected to CuratorSearch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CuratorSearch MCP server still maintained?
CuratorSearch is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the CuratorSearch MCP server?
VerifyMCP ran 13 checks on CuratorSearch, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.