Ext Ops Panel
Open dashboard
Comparison

veritasacta-verify vs BLEA

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). BLEA is an MCP server published by Nitmi. Marketplaces we read that list it: 2 (Official MCP Registry, Copilot CLI: github/awesome-copilot). As of our marketplace pass on 2026-10-12. 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-verifyBLEA
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.7.0
Forks (GitHub): 0
Stars (GitHub): 11
Not marked · First seen
Copilot CLI: github/awesome-copilot Not listed Listed
Version: 0.6.1
Forks (GitHub): 0
Stars (GitHub): 11
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 BLEA
Factveritasacta-verifyBLEA
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)8 (worse)11 (better)
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (blea)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)12
Licence (differs)Not statedMIT
Repository (differs)github.com/veritasacta/actagithub.com/nitmi/blea
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.

BLEA

In its own words, on Official MCP Registry:

Safe BLE diagnostics, evidence workflows, and guarded automation for AI agents.

How to run each

veritasacta-verify

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

BLEA As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio blea -- uvx blea

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: veritasacta-verify · What it can do: BLEA · 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. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. 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