Delv
CommunitySlow· 2mo4.3by Justin Molano

Smithsonian MCP

Searches 3M+ Smithsonian Open Access objects across art, history, and science collections with 16 tools.

B
Safety & Trust

Delv Safety Grade: B

Score 72/100 · assessed 2026-04-18

Maintainer55
Permissions92
Supply chain75
Transparency68
Incidents100

Smithsonian MCP is a community-built wrapper around the official Smithsonian Open Access API, offering read-only access to over three million museum objects. The server is maintained by a solo developer (Justin Molano) with a reasonable GitHub presence but limited track record. Permissions are extremely scoped: it only reads from a public API and requires a Smithsonian API key, which is freely available. The package ships via npm with standard installation, though documentation is basic and the repository shows modest activity. No security incidents are known. The narrow scope (read-only cultural data) and use of an official government API significantly limit risk, but the solo maintainer and thin community support mean you're relying on one person's availability for updates or fixes.

Green flags

  • Read-only access to official Smithsonian public API, no write capabilities
  • Extremely narrow scope: cultural heritage data only, no filesystem or shell
  • Standard npm distribution with versioning and clear install path
  • Wraps a legitimate government API with established terms of service
  • No known security incidents or malicious activity

Red flags

  • Solo maintainer with limited public track record or community backing
  • Thin documentation and sparse repository activity (low commit frequency)
  • No evidence of security review or testing beyond basic functionality
  • Requires API key in environment, potential for accidental exposure if mishandled

Permissions requested

Outbound networkRead env
Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Install

npx -y @molanojustin/smithsonian-mcp
Env vars needed: SMITHSONIAN_API_KEY

Review

Smithsonian MCP wraps the Smithsonian Open Access API, giving Claude direct access to over three million museum objects spanning art, history, and science. You get 16 tools for searching collections, fetching object details, filtering by date or medium, and pulling images. It's a proper research assistant for anyone working with cultural heritage data. I'd reach for this when building educational content, fact-checking historical claims, or sourcing public domain imagery. Say you're writing about early aviation: you can search for Wright Brothers artefacts, filter by date range, pull high-resolution images, and get curatorial metadata in one pass. The API returns structured JSON with titles, descriptions, dates, physical dimensions, and direct links to assets. No scraping, no rate limit headaches if you've got an API key. The 16 tools feel comprehensive without being overwhelming. You've got basic search, advanced filtering by type or topic, image retrieval, and object detail lookups. The API key requirement is straightforward: register on the Smithsonian site, paste it into your environment, done. The server handles pagination and returns clean results. Quirks: the Smithsonian API itself can be slow during peak hours, and not every object has high-resolution images. Some records are sparse on metadata, especially older acquisitions. The search tools are only as good as the Smithsonian's own cataloguing, which varies wildly by collection. You'll get pristine records for flagship pieces and patchy data for obscure items. This isn't a general-purpose image search tool. It's for people who need authoritative museum data: educators building lesson plans, writers researching historical periods, developers prototyping heritage apps. If you're just looking for stock photos, use something else. If you need to cite sources or verify provenance, this is gold. The public domain status of most objects makes it especially useful for commercial projects that need legally clear imagery.
Verdict

Install this if you regularly work with historical research, museum content, or educational materials. The Smithsonian's collection is vast and the API is well-documented. Skip it if you're not specifically interested in cultural heritage data or if you need faster, more general image search.

Good at

  • Three million objects with authoritative metadata beats scraping museum sites yourself.
  • Most content is public domain, making it safe for commercial use without licensing headaches.
  • 16 tools cover the full workflow from search to image download without needing multiple APIs.
  • Free API key with generous rate limits for non-commercial use.
  • Returns structured JSON with curatorial details you won't find in generic image databases.

Watch out

  • API response times can lag during peak hours, slowing down batch operations.
  • Metadata quality varies wildly between collections, with older items often lacking detail.
  • Not all objects have high-resolution images available, limiting use for print or large displays.
  • Search relevance depends entirely on Smithsonian cataloguing, which isn't always consistent.
  • Requires manual config for hosts beyond Claude Desktop.

Use cases

  • museum research
  • historical artefact lookups
  • science education
  • heritage content generation

Getting started

1. Register for a free Smithsonian API key at api.si.edu/signup and save it. 2. Run `npx -y @molanojustin/smithsonian-mcp` to install, then add it to your Claude Desktop config with `SMITHSONIAN_API_KEY` in the env block. 3. Restart Claude Desktop and verify by asking it to search for a specific artefact, like 'Apollo 11 command module'. 4. Test image retrieval on an object to confirm media links work. 5. Watch out for slow responses during US daytime hours when the API is busiest.

Works with

Claude DesktopClaude CodeCursor

Similar MCPs