WolframAlpha vs vvuq4ai
WolframAlpha is an MCP server published by SecretiveShell. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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). 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
| Marketplace |  WolframAlpha |  vvuq4ai |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:4cd89d002d55 Forks (GitHub): 21 Pulls (Docker Hub): 47 521 Stars (Docker Hub): 6 Stars (GitHub): 75 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.3.0 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
| Fact | WolframAlpha | vvuq4ai |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 75 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 47 521 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 21 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/wolfram-alpha) | Remote server (vvuq.dirkenglund.org/mcp) |
| Transport (differs) | stdio | SSE |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/secretiveshell/mcp-wolfram-alpha | github.com/dirkenglund/vvuq4ai-plugin |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (32 h ago) |
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
WolframAlpha
Connect your chat repl to wolfram alpha computational intelligence.
vvuq4ai
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.
How to run each
WolframAlpha As a local MCP server: Docker image
claude mcp add --env "WOLFRAM_API_KEY=<YOUR_WOLFRAM_API_KEY>" --transport stdio wolfram-alpha -- docker run -i --rm -e WOLFRAM_API_KEY mcp/wolfram-alphaRequires: WOLFRAM_API_KEY (secret)
vvuq4ai As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install vvuq4ai@claude-communityCommands 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
The marketplaces of vvuq4ai publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of vvuq4ai publish no settings it asks for, so we do not compare settings.
What it can do: WolframAlpha · What it can do: vvuq4ai · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.