rijksmuseum
No liveness check has reached it yet; it has been in the index since 10 Oct 2026. How this is checked
Rijksmuseum MCP Server exposes tools for searching the Rijksmuseum’s collection, retrieving complete object records, and obtaining IIIF image URLs. It provides a keyless JSON-RPC endpoint for developers and AI assistants working with Dutch art and cultural heritage data.
Inferred · not functionally tested
Overview
6 featuresPurpose: Finding authoritative Rijksmuseum collection records and image URLs through a machine-readable interface.
Inferred · not functionally tested
Audience: developers building museum, cultural heritage, and research applications
Inferred · not functionally tested
Functions: data_extraction
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: unknown · Self-hosting: unknown
Recorded constraints: pricing: free · license: Proprietary · platforms: WEB · deployment: browser, api_only, cloud_managed
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: gateway.pipeworx.io. These links do not verify the individual claims.
In the API design, testing & docs space, rijksmuseum takes a focused approach. Inferred · not functionally tested: It focuses on finding authoritative Rijksmuseum collection records and image URLs through a machine-readable interface. Inferred · not functionally tested: It is built as an open-source project for developers building museum, cultural heritage, and research applications. Basis unknown · not verified: rijksmuseum is free to use. Basis unknown · not verified: rijksmuseum is available on the web and API.
It is developed by Pipeworx (Netherlands). Inferred · not functionally tested: Among its 6 catalogued features are collection search, object lookup, and IIIF image URLs. Inferred · not functionally tested: Catalogued interfaces include an MCP server.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Collection search
- Object lookup
- IIIF image URLs
- JSON-RPC endpoint
- MCP tools
- Field-scoped filters
Topics: Inferred · not functionally tested
Built with & integrations
- Cloudflare
- cf-ray header
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed10 Oct · 00:02 UTCRijksmuseum seen via MCP Registry (official)Source: MCP Registry (official) · Open
Frequently asked questions about rijksmuseum
- What is rijksmuseum?
- Inferred · not functionally tested: Rijksmuseum focuses on finding authoritative Rijksmuseum collection records and image URLs through a machine-readable interface. It is catalogued under API design, testing & docs on PulseGate.
- Who is rijksmuseum for?
- Inferred · not functionally tested: rijksmuseum is an open-source project built for developers building museum, cultural heritage, and research applications.
- Is rijksmuseum free?
- Basis unknown · not verified: Yes — rijksmuseum is free to use.
- What platforms does rijksmuseum run on?
- Basis unknown · not verified: rijksmuseum runs on the web and API.
- Is rijksmuseum still active?
- Unverified. rijksmuseum has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
- What are alternatives to rijksmuseum?
- Similar projects tracked by PulseGate include metmuseum, riksdagen-se, and knmi.metmuseumriksdagen-seknmi
- Who makes rijksmuseum?
- rijksmuseum is developed by Pipeworx, based in the Netherlands.
- Does rijksmuseum have an API or integrations?
- Inferred · not functionally tested: Yes — rijksmuseum exposes an MCP server.
Similar projects
Closest matches by what these projects do