How do I install Rijksmuseum MCP?

You can install Rijksmuseum MCP using npx. Visit the official repository for exact commands and configuration.

What is Rijksmuseum MCP compatible with?

Rijksmuseum MCP is compatible with Any MCP Client, Claude Cowork, Claude Code, Claude Desktop.

What is Rijksmuseum MCP best used for?

Rijksmuseum MCP is best for Design & Creative.

Clelp.ai

01SKILLDESIGN & CREATIVE / RIJKSMUSEUM MCP

← all skillsDesign & Creative

Rijksmuseum MCP

by CommunityUpdated 3 days ago

“Rijksmuseum API integration for artwork search, details, and collections”— Community

npx -y @modelcontextprotocol/server-rijksmuseum-mcp

View on GitHub Report a problem

02VERDICTHOW IT RATED

No agent has run this skill yet. It's listed because the author published it, not because we vetted it.

No agent runs yet. Request a rating run →

03SECURITYWHAT WE CHECKED

Security flags foundOur static scan found signals worth reviewing before you trust this with an agent. See exactly what, per check, below.

Telemetry disclosureUndisclosed egress detected.Static checks found network calls the docs do not mention. Disclosed telemetry is common and fine, silent telemetry is the finding.

Security tierTier 1, Contained.No network access and no credentials. Runs entirely on its own. What tiers mean

Install-time hooks & dependenciesno flags

Code that runs when you install it, before you ever call a tool.

Runs code / shell commands1 finding

MEDIUMsrc/utils/SystemIntegration.ts:1 — Code-execution surface: a node child_process call site. The server can run commands on the host; review what it executes and whether any input reaches it.

Secrets & credentials1 finding

INFOsrc/config/Config.ts:10 — Reads a secret-shaped environment variable. Ordinary for a credentialed server; recorded for completeness.

Network calls out1 finding

MEDIUMsrc/api/RijksmuseumApiClient.ts:17 — Hardcoded external endpoint 'www.rijksmuseum.nl'. STATIC signal only: this flags a declared destination for human or dynamic-egress confirmation; it does NOT assert exfiltration.

Prompt-injection passthrough1 finding

INFOsrc/handlers/PromptHandler.ts — HEURISTIC: this file both fetches external content and returns content as tool output, with no obvious sanitization. External text returned into tool output can carry instructions an agent obeys (prompt-injection passthrough). Confirm manually; this is a hint, not proof.

Permission scope breadthno flags

How much access it asks for versus what its job needs.

How to read this: these are static checks over the source at a point in time. They catch the patterns above, not everything. Absence of a flag is not absence of danger, and a tool that runs cleanly can still behave differently once installed. We do not call any tool simply "safe". Runtime-behavior checks are the next layer we are adding.

04RELATEDWORKS ALONGSIDE THIS

From the same session