Ext Ops Panel
Open dashboard
Comparison

vvuq4ai vs BLEA

vvuq4ai is a plugin bundle for AI coding tools published by dirkenglund. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). 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-15. 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
Marketplacevvuq4aiBLEA
Claude Code: claude-plugins-community Listed
Version: 0.3.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.7.0
Downloads/month (PyPI): 423
Downloads/week (PyPI): 51
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

vvuq4ai vs BLEA
Factvvuq4aiBLEA
Marketplaces that list it22
Stars (GitHub) (differs)0 (worse)11 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (vvuq.dirkenglund.org/mcp)On your machine (blea)
Transport (differs)SSEstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)12
LicenceMITMIT
Repository (differs)github.com/dirkenglund/vvuq4ai-plugingithub.com/nitmi/blea
Changes in the last 7 days (differs)20
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)Answered with HTTP 404 (2 days ago)no remote endpoint we check

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

vvuq4ai

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

Verify AI-generated STEM claims against curated knowledge bases, IEEE standards, and mathematical checks. VVUQ4AI runs physics constants, dimensional analysis, and standards compliance checks (IEEE 802.3, NSF Biosketch) on claims Claude generates or encounters, returning structured verdicts with confidence scores.

BLEA

In its own words, on Official MCP Registry:

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

How to run each

vvuq4ai As a Claude Code plugin

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

BLEA As a local MCP server: PyPI package

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

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

Only vvuq4ai 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: vvuq4ai · 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 public marketplace files in GitHub repositories of their authors. 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