Ext Ops Panel
Open dashboard
Comparison

sourceverify vs io.github.Clawdio777/verity

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.Clawdio777/verity is an MCP server published by Clawdio777. 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.Clawdio777/verity
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.2
Downloads/month (npm): 414
Downloads/week (npm): 39
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

sourceverify vs io.github.Clawdio777/verity
Factsourceverifyio.github.Clawdio777/verity
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (verity-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/sourceverify-ai/sourceverify-skillgithub.com/clawdio777/verity
Changes in the last 7 days00
First seen (differs)2026-10-122026-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

sourceverify

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

Verify academic citations and references using the SourceVerify API

io.github.Clawdio777/verity

In its own words, on Official MCP Registry:

Real-time fact-checking MCP. Verifies claims against live sources with structured verdicts.

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.Clawdio777/verity As a local MCP server: npm package

Claude Code
claude mcp add --env "VERITY_PRIVATE_KEY=<YOUR_VERITY_PRIVATE_KEY>" --transport stdio verity -- npx -y verity-mcp

Requires: VERITY_PRIVATE_KEY (secret)

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 sourceverify publish no settings it asks for, so we do not compare settings.

What it can do: sourceverify · What it can do: io.github.Clawdio777/verity · 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