Ext Ops Panel
Open dashboard
Comparison

Contentrain vs CiteRank MCP

Contentrain is an MCP server published by Contentrain. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). CiteRank MCP is an MCP server published by WebforMike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
MarketplaceContentrainCiteRank MCP
Official MCP Registry Listed
Version: 3.11.1
Downloads/month (npm): 14 403
Downloads/week (npm): 3 344
Forks (GitHub): 0
Stars (GitHub): 6
Not marked · First seen
Listed
Version: 2.0.2
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

Contentrain vs CiteRank MCP
FactContentrainCiteRank MCP
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)6No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server or your machineRemote server (citerankscore.com/api/mcp-server)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)8Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/contentrain/aiNot stated
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11
Endpoint at the last checknot checked yetnot checked yet

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

Contentrain

In its own words, on Official MCP Registry:

Git-native content governance for AI agents — 27 deterministic MCP tools over stdio and HTTP.

CiteRank MCP

In its own words, on Official MCP Registry:

Full AI visibility audits: schema, citations, agentic readiness, agent journeys, WordPress deploys.

How to run each

Contentrain As a Claude Code plugin

Claude Code
/plugin marketplace add contentrain/ai
/plugin install contentrain@contentrain

Requires: Authorization header

CiteRank MCP As a remote MCP server

Claude Code
claude mcp add --transport http citerank https://citerankscore.com/api/mcp-server --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

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

What it can do: Contentrain · What it can do: CiteRank MCP · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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