Ext Ops Panel
Open dashboard
Comparison

Tuning Engines - Governed AI Runtime vs Perceptdot Core

Tuning Engines - Governed AI Runtime is an MCP server published by cerebrixos-org. Marketplaces we read that list it: 1 (Official MCP Registry). Perceptdot Core is an MCP server published by perceptdot. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
MarketplaceTuning Engines - Governed AI RuntimePerceptdot Core
Official MCP Registry Listed
Version: 0.4.34
Downloads/month (npm): 702
Downloads/week (npm): 192
Forks (GitHub): 4 (last published figure)
Stars (GitHub): 6 (last published figure)
Not marked · First seen
Listed
Version: 0.1.0
Downloads/month (npm): 130
Downloads/week (npm): 33
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

Tuning Engines - Governed AI Runtime vs Perceptdot Core
FactTuning Engines - Governed AI RuntimePerceptdot Core
Marketplaces that list it11
Stars (GitHub) (differs)6 (last published figure)No figure on GitHub
Forks (GitHub) (differs)4 (last published figure)No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (tuningengines-cli)On your machine (@perceptdot/core)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/cerebrixos-org/tuning-engines-cliNot stated
Changes in the last 7 days (differs)40
First seen2026-10-112026-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

Tuning Engines - Governed AI Runtime

In its own words, on Official MCP Registry:

Govern model, agent, skill, and MCP workflows with policy, approvals, traces, and usage analytics.

Perceptdot Core

In its own words, on Official MCP Registry:

B2A2H MCP server — AI agent app store. Auto-discover and recommend MCP servers for any project.

How to run each

Tuning Engines - Governed AI Runtime As a local MCP server: npm package

Claude Code
claude mcp add --env "TE_API_KEY=<YOUR_TE_API_KEY>" --transport stdio tuning-engines -- npx -y tuningengines-cli mcp serve

Requires: TE_API_KEY (secret)

Perceptdot Core As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio core -- npx -y @perceptdot/core

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

What it can do: Tuning Engines - Governed AI Runtime · What it can do: Perceptdot Core · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.

Where the data comes from: how the catalog is built