Ext Ops Panel
Open dashboard
Comparison

sourceverify vs io.github.dorianfields/x402-cite-check

sourceverify is a plugin bundle for AI coding tools published by SourceVerify-ai. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.dorianfields/x402-cite-check is an MCP server published by dorianfields. 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
Marketplacesourceverifyio.github.dorianfields/x402-cite-check
Claude Code: claude-plugins-community Listed
Version: 0.1.0-beta
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

sourceverify vs io.github.dorianfields/x402-cite-check
Factsourceverifyio.github.dorianfields/x402-cite-check
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (hermes-earn.tailea28c0.ts.net/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/sourceverify-ai/sourceverify-skillNot stated
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-13

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

sourceverify

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

Verify academic citations and references using the SourceVerify API

io.github.dorianfields/x402-cite-check

In its own words, on Official MCP Registry:

Verify cited URLs still resolve: reachability, HTTP status and page title. x402-paid.

How to run each

sourceverify As a Claude Code plugin

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

io.github.dorianfields/x402-cite-check As a remote MCP server

Claude Code
claude mcp add --transport http x402-cite-check https://hermes-earn.tailea28c0.ts.net/mcp

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

Only io.github.dorianfields/x402-cite-check 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: sourceverify · What it can do: io.github.dorianfields/x402-cite-check · 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