Ext Ops Panel
Open dashboard
Comparison

namejam vs Namesake — baby name catalog and guides

namejam is a plugin bundle for AI coding tools published by FireflySentinel. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Namesake — baby name catalog and guides is an MCP server published by namesake.baby. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
MarketplacenamejamNamesake — baby name catalog and guides
Claude Code: claude-plugins-community Listed
Version: eccd052
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
No figure published
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

namejam vs Namesake — baby name catalog and guides
FactnamejamNamesake — baby name catalog and guides
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (namesake.baby/api/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/fireflysentinel/namejamNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 307 (4 days ago)

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

namejam

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

Generate available project names with taste — checks GitHub, npm, PyPI, and domain availability. Reads your project context, generates short memorable names (think Stripe, Linear, Notion), and shows only names you can actually use.

Namesake — baby name catalog and guides

In its own words, on Official MCP Registry:

Read-only access to Namesake's baby name catalog: meaning, origin, pronunciation, popularity trend.

How to run each

namejam As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install namejam@claude-community

Namesake — baby name catalog and guides As a remote MCP server

Claude Code
claude mcp add --transport http discovery https://namesake.baby/api/mcp

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

Only Namesake — baby name catalog and guides has a remote endpoint we check. How we check endpoints

Tools each declares

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

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: namejam · What it can do: Namesake — baby name catalog and guides · Compare two other plugins

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