Ext Ops Panel
Open dashboard
Comparison

veracityapi vs io.github.carlisia/mcp-factcheck

veracityapi is a plugin bundle for AI coding tools published by psyduckler. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.carlisia/mcp-factcheck is an MCP server published by carlisia. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
Marketplaceveracityapiio.github.carlisia/mcp-factcheck
Claude Code: claude-plugins-community Listed
Version: 59520cc
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 3
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

veracityapi vs io.github.carlisia/mcp-factcheck
Factveracityapiio.github.carlisia/mcp-factcheck
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub3
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (ghcr.io/carlisia/mcp-factcheck:v1.0.0)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/psyduckler/veracityapigithub.com/carlisia/mcp-factcheck
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

veracityapi

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

VeracityAPI gives Claude content verification tools for text, image, audio, and batch workflows. It helps agents triage AI-generated, manipulated, risky, or low-trust content before publishing, citing, moderating, accepting uploads, or using content as training data. Results include deterministic risk signals, evidence, and recommended_action routing such as allow, revise, human_review, or reject.

io.github.carlisia/mcp-factcheck

In its own words, on Official MCP Registry:

An MCP server that validates content against MCP specification using semantic search and AI

How to run each

veracityapi As a Claude Code plugin

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

io.github.carlisia/mcp-factcheck As a local MCP server: Docker image

Claude Code
claude mcp add --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio mcp-factcheck -- docker run -i --rm -e OPENAI_API_KEY ghcr.io/carlisia/mcp-factcheck:v1.0.0

Requires: OPENAI_API_KEY

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

What it can do: veracityapi · What it can do: io.github.carlisia/mcp-factcheck · 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