Rijksmuseum
NPM · @PIPEWORX/MCP-RIJKSMUSEUM · 2 COMPONENTS
Rijksmuseum — the Dutch national museum's collection, via its open Data Services API…
Available components
Last scanned (7 hours ago)
Scores higher than 72% of npm servers
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-rijksmuseum). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 712 tokens (~237/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 2 Nov 26 +2
- Stability: unverified → 0.13 ▲ functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-rijksmuseum@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-rijksmuseum |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-rijksmuseum/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3691886857 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4d6a473c69c16c89c6f67509c900b938846401015ef12031a27b352571af90d10b39d303d2996a62a248cf1717ef97534a9f421d130e33dbcafcac9e6 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
rijks_object ~156
One Rijksmuseum object in full: title, maker, date, object type, materials, place, depicted subjects, the museum's own curatorial description, object number, rights statement and image URL. Accepts the numeric object id, its id.rijksmuseum.nl URI, or a museum object number such as "SK-C-5" (resolved for you). Keyless. Example: rijks_object({ id: "200107928" }) → The Night Watch.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Numeric object id ("200107928"), its id.rijksmuseum.nl URI, or an object number ("SK-C-5"). |
| object_number | string | – | Alias for `id` when you hold a museum object number. |
No output schema declared.
No examples provided.
rijks_object_image ~154
Image URLs for one Rijksmuseum object: the IIIF Image API 3 service, full-resolution pixel dimensions, a full-size JPEG, a scaled JPEG at a width you choose, a thumbnail, and the object's rights statement (most of the collection is public domain). Says plainly when an object has no published image rather than returning a broken link. Keyless. Example: rijks_object_image({ id: "200107928", width: 1200 }).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Numeric object id, e.g. "200107928", or its id.rijksmuseum.nl URI. |
| width | number | – | Pixel width for image_scaled_url, 100-4000. Default 1000. |
No output schema declared.
No examples provided.
rijks_search ~347
Search the Rijksmuseum's ~800,000-object collection — Dutch Golden Age paintings, prints, drawings, photographs, Delftware, Asian art — by title, maker, object type, material, technique or object number, and get back real records: title, maker, date, materials, curatorial description, rights and a IIIF image URL. AUTHORITATIVE for what the Dutch national museum holds and how it catalogues it. Keyless. There is no free-text `q`: filters are field-scoped, and titles are catalogued in Dutch. Example: rijks_search({ creator: "Rembrandt", type: "painting", limit: 5 }).
| Name | Type | Req | Description |
|---|---|---|---|
| creator | string | – | Maker name, e.g. "Rembrandt van Rijn" or "Vermeer". |
| imageAvailable | boolean | – | Only objects that have a published image. |
| limit | number | – | How many hits to hydrate into full records, 1-25. Default 10. Each costs one upstream fetch. |
| material | string | – | Material, e.g. "canvas", "paper", "oil paint". |
| objectNumber | string | – | Exact museum object number, e.g. "SK-C-5". |
| page_token | string | – | next_page_token from a previous call, to continue through the result set. |
| technique | string | – | Technique, e.g. "etching", "engraving". |
| title | string | – | Words in the object title, as catalogued (Dutch), e.g. "Nachtwacht". |
| type | string | – | Object type, e.g. "painting", "print", "drawing", "photograph". |
No output schema declared.
No examples provided.
How do I install the Rijksmuseum MCP server?
Rijksmuseum runs locally as an npm package, launched with npx -y @pipeworx/mcp-rijksmuseum. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-rijksmuseum
claude mcp add pipeworx-io-rijksmuseum -- npx -y @pipeworx/mcp-rijksmuseum
What is the Rijksmuseum MCP server?
Rijksmuseum is an MCP server listed in the public MCP registry as io.github.pipeworx-io/rijksmuseum. Rijksmuseum, the Dutch national museum's collection, via its open Data Services API… This page covers its npm package (@pipeworx/mcp-rijksmuseum).
Is the Rijksmuseum MCP server safe to use?
Rijksmuseum scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Rijksmuseum MCP server expose?
Rijksmuseum exposes 3 tools: rijks_search, rijks_object, rijks_object_image. Their descriptions and schemas cost roughly 657 tokens of context every time the server is loaded.
Is the Rijksmuseum MCP server still maintained?
Rijksmuseum is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Rijksmuseum MCP server under?
Rijksmuseum declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.