Ext Ops Panel
Open dashboard
Comparison

CONTENTdm State Archives vs io.github.mrfentmen/smithsonian-mcp

CONTENTdm State Archives is an MCP server published by ianderso. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.mrfentmen/smithsonian-mcp is an MCP server published by mrfentmen. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceCONTENTdm State Archivesio.github.mrfentmen/smithsonian-mcp
Official MCP Registry Listed
Version: 0.1.0
Downloads/month (PyPI): 0
Downloads/week (PyPI): 34
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.2
Downloads/month (npm): 725
Downloads/week (npm): 27
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

CONTENTdm State Archives vs io.github.mrfentmen/smithsonian-mcp
FactCONTENTdm State Archivesio.github.mrfentmen/smithsonian-mcp
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (contentdm-mcp)On your machine (smithsonian-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)6, secrets among them: 0Not published
LicenceNot statedNot stated
Repository (differs)github.com/ianderso/contentdm-mcpgithub.com/mrfentmen/awesome-mcps
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

CONTENTdm State Archives

In its own words, on Official MCP Registry:

Search US state archives' record images on CONTENTdm; read items, pages and transcripts.

io.github.mrfentmen/smithsonian-mcp

In its own words, on Official MCP Registry:

MCP server for Smithsonian collections: artifacts, art, specimens. Free key.

How to run each

CONTENTdm State Archives As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio contentdm-mcp -- uvx contentdm-mcp

io.github.mrfentmen/smithsonian-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio smithsonian-mcp -- npx -y smithsonian-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of io.github.mrfentmen/smithsonian-mcp publish no settings it asks for, so we do not compare settings.

What it can do: CONTENTdm State Archives · What it can do: io.github.mrfentmen/smithsonian-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built