# Rijksmuseum (npm · @pipeworx/mcp-rijksmuseum)

Rijksmuseum — the Dutch national museum's collection, via its open Data Services API…

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 69/100, [markdown](https://verifymcp.io/servers/pipeworx-io-rijksmuseum/rijksmuseum-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-rijksmuseum/rijksmuseum-mcp)
- npm · `@pipeworx/mcp-rijksmuseum`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-rijksmuseum/pipeworx-mcp-rijksmuseum.md), [page](https://verifymcp.io/servers/pipeworx-io-rijksmuseum/pipeworx-mcp-rijksmuseum)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-rijksmuseum`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-rijksmuseum).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-rijksmuseum -- npx -y @pipeworx/mcp-rijksmuseum
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-rijksmuseum": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-rijksmuseum"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-rijksmuseum": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-rijksmuseum"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-rijksmuseum -- npx -y @pipeworx/mcp-rijksmuseum
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-rijksmuseum": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-rijksmuseum"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-rijksmuseum --command npx --arg -y --arg @pipeworx/mcp-rijksmuseum
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-rijksmuseum:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-rijksmuseum"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-rijksmuseum": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-rijksmuseum"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-rijksmuseum -t stdio -c npx -a -y @pipeworx/mcp-rijksmuseum
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-rijksmuseum": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-rijksmuseum"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 82, +1)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.17 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-02 (score 81, +2)

- [functional improvement] Stability: unverified → 0.13

### 2026-10-31 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (3)

### `rijks_search` (~347 tokens)

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 }).

Input parameters:

- `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".

### `rijks_object` (~156 tokens)

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.

Input parameters:

- `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.

### `rijks_object_image` (~154 tokens)

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 }).

Input parameters:

- `id` (string, required): Numeric object id, e.g. "200107928", or its id.rijksmuseum.nl URI.
- `width` (number): Pixel width for image_scaled_url, 100-4000. Default 1000.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-rijksmuseum/pipeworx-mcp-rijksmuseum#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-rijksmuseum
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-rijksmuseum
- Repository: https://github.com/pipeworx-io/mcp-rijksmuseum
- Website: https://pipeworx.io/packs/rijksmuseum
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-rijksmuseum/pipeworx-mcp-rijksmuseum.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-rijksmuseum/pipeworx-mcp-rijksmuseum.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-rijksmuseum/pipeworx-mcp-rijksmuseum