Ext Ops Panel
Open dashboard
Comparison

mcp-server-dev vs Chronicling America

mcp-server-dev is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-official). Chronicling America is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
Marketplacemcp-server-devChronicling America
Claude Code: claude-plugins-official Listed
Version: not stated
Forks (GitHub): 4 858
Stars (GitHub): 46 630
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.1
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

mcp-server-dev vs Chronicling America
Factmcp-server-devChronicling America
Marketplaces that list it11
Stars (GitHub) (differs)46 630 (better)0 (worse)
Forks (GitHub) (differs)4 858 (better)0 (worse)
Last release (differs)Not published2026-10-31
Where it runs (differs)Installs as a plugin bundleRemote server (gateway.pipeworx.io/chronicling-america/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)3Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/anthropics/claude-plugins-officialgithub.com/pipeworx-io/mcp-chronicling-america
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 36 h ago returned HTTP 200

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

mcp-server-dev

In its own words, on Claude Code: claude-plugins-official:

Skills for designing and building MCP servers that work seamlessly with Claude. Guides you through deployment models (remote HTTP, MCPB, local), tool design patterns, auth, and interactive MCP apps.

Chronicling America

In its own words, on Official MCP Registry:

Chronicling America MCP — full-text search of ~150 years of digitized U.S. newspapers…

How to run each

mcp-server-dev As a Claude Code plugin

Claude Code
/plugin install mcp-server-dev@claude-plugins-official

Chronicling America As a remote MCP server

Claude Code
claude mcp add --transport http chronicling-america https://gateway.pipeworx.io/chronicling-america/mcp

Requires: PIPEWORX_API_KEY (secret)

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

Only Chronicling America has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of mcp-server-dev nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

The marketplaces of mcp-server-dev publish no settings it asks for, so we do not compare settings.

What it can do: mcp-server-dev · What it can do: Chronicling America · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. 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