Ext Ops Panel
Open dashboard
Comparison

veritasacta-verify vs VerifyAPI — fact-check with signed receipts

veritasacta-verify is a plugin bundle for AI coding tools published by VeritasActa. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). VerifyAPI — fact-check with signed receipts is an MCP server published by KyTheKitty. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplaceveritasacta-verifyVerifyAPI — fact-check with signed receipts
Claude Code: claude-plugins-community Listed
Version: c801781
Forks (GitHub): 2
Stars (GitHub): 8
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.9
Downloads/month (npm): 531
Downloads/week (npm): 57
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

veritasacta-verify vs VerifyAPI — fact-check with signed receipts
Factveritasacta-verifyVerifyAPI — fact-check with signed receipts
Marketplaces that list it11
Stars (GitHub) (differs)8 (better)0 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@verify-api/mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/veritasacta/actagithub.com/kythekitty/verifyapi-mcp
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

veritasacta-verify

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

Offline Ed25519 receipt verifier — checks signed decision receipts, agent manifests, and audit bundles without contacting any server.

VerifyAPI — fact-check with signed receipts

In its own words, on Official MCP Registry:

Fact-check any claim with live web sources. Ed25519-signed receipts. Catches hallucinations.

How to run each

veritasacta-verify

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

VerifyAPI — fact-check with signed receipts As a local MCP server: npm package

Claude Code
claude mcp add --env "VERIFYAPI_API_KEY=<YOUR_VERIFYAPI_API_KEY>" --transport stdio verifyapi -- npx -y @verify-api/mcp

Requires: VERIFYAPI_API_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 veritasacta-verify publish no settings it asks for, so we do not compare settings.

What it can do: veritasacta-verify · What it can do: VerifyAPI — fact-check with signed receipts · 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