mcpbeat

Smithsonian MCP Server

io.github.cyanheads/smithsonian-mcp-server
answering

Smithsonian MCP Server is answering right now. Last checked 4 min ago. 330 installs a week from npm. It exposes 6 tools. Last commit 30 Jul 2026.

Search 14.5M Smithsonian Open Access objects, get CC0 images, find cross-collection connections.

Installs per day peak 401 · avg 87 · -48% w/w
a month agotoday
Uptime history 42 hours of history · worst hour 75%
42 hours agonow
100.0%
Uptime 24h
91 of 91 checks
6
Tools
read from the server
374 ms
Response time
average over 24h
330
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add smithsonian-mcp-server --transport http https://smithsonian.caseyjhand.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "smithsonian-mcp-server": {
      "url": "https://smithsonian.caseyjhand.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.smithsonian-mcp-server]
url = "https://smithsonian.caseyjhand.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "smithsonian-mcp-server": {
      "url": "https://smithsonian.caseyjhand.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "smithsonian-mcp-server": {
      "url": "https://smithsonian.caseyjhand.com/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

smithsonian
smithsonian_browse_category
Browse Smithsonian objects within one exact category — a single museum (mode "museum"), culture, indexed date term (mode "period"), object type (mode "medium"), or subject term (mode "topic"). The value must be an exact indexed category term, not free text: resolve museum, culture, period, and topic vocabulary with smithsonian_list_terms first (object_type is not enumerable there — harvest it from smithsonian_search_objects results, and treat each casing as its own category, since a harvested object_type covers only the casing it was written in). Returns the category total count, a page of matching objects, and a museum breakdown of that page; page the full category with start and rows. For open-ended or topic discovery, start with smithsonian_search_objects instead.
smithsonian_find_related
Discover objects across Smithsonian collections related to a given anchor object, matched on shared metadata signals — culture, period, object type, named parties, and topic terms. Each related object is tagged with the signals that connected it to the anchor; a named-party signal carries the catalog's own role for that party (maker, Collector, Donor, issuing authority, …), not a fixed "maker" label. Matches surface across museums — an NASM aerospace anchor can pull related objects from NMNHPALEO, SAAM, and NMAH.
smithsonian_get_media
Return every CC0 (open-access) image for a Smithsonian object at multiple resolutions. The tool never returns an empty list — it names the reason instead: an object with nothing digitized, an object whose media is entirely non-image (scanned books, 3D models, sound recordings), and an object whose images are entirely non-CC0 each fail with their own reason. Each image entry includes thumbnail (~120px), screen-size (~800px), and high-resolution JPEG/TIFF URLs with pixel dimensions. The cc0_only filter on smithsonian_search_objects surfaces objects that have downloadable CC0 images.
smithsonian_get_object
Fetch a normalized catalog metadata projection for a Smithsonian object by its record_id (from smithsonian_search_objects results). Returns the exposed catalog fields — title, dates, description, makers, materials, dimensions, places, cultures, topics, exhibitions, credit line, identifiers, rights, and a media summary. The media summary is a count; full image URLs come from smithsonian_get_media.
smithsonian_list_terms
Enumerate the valid term vocabulary for an indexed Smithsonian filter field (unit_code, culture, place, date, online_media_type, topic). Terms are a controlled vocabulary — often plural or qualified (e.g. "Paintings", not "Painting") — so guessed filter values tend to return nothing. Returns a page of the field's distinct term values; large vocabularies (topic has 133k terms, place 114k) page via start and rows. For unit_code, each code is returned with its museum name and contains matches the name as well as the code, so a museum name resolves to its code in one call.
smithsonian_search_objects
Recommended first step for open-ended or topic discovery: free-text search across 14.5 million Smithsonian objects, with optional exact filters. Filters narrow by museum unit, object type, indexed date term, culture, geographic place, subject topic, named party, and online/CC0 availability. Returns curated summaries (title, date, museum, thumbnail URL, CC0 flag) with the total match count. The record_id in each result is the identifier for smithsonian_get_object, smithsonian_find_related, and smithsonian_get_media. To browse one exact category — a single museum, culture, date term, object type, or topic — use smithsonian_browse_category instead.

Endpoints

URLTransportStateLatencyChecked
https://smithsonian.caseyjhand.com/mcp streamable-http answering 430 ms 4 min ago

Smithsonian MCP Server — questions

Answers built from our own checks of this server.

What can Smithsonian MCP Server do?
It exposes 6 tools, read directly from the server on our last check. Among them: smithsonian_browse_category, smithsonian_find_related, smithsonian_get_media, smithsonian_get_object, smithsonian_list_terms, smithsonian_search_objects. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Smithsonian MCP Server working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 374 ms. The bar chart above shows every period we have measured.
How do I connect Smithsonian MCP Server?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Smithsonian MCP Server need an API key?
No. Smithsonian MCP Server completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Smithsonian MCP Server?
It answers our handshake in 374 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Smithsonian MCP Server?
The npm package @cyanheads/smithsonian-mcp-server was installed 330 times in the last week. Week over week that is -48%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Smithsonian MCP Server open source?
Yes — it is published under the Apache-2.0 licence, written in TypeScript and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.