Deploy to Agents vs Tuning Engines - Governed AI Runtime
Deploy to Agents is an MCP server published by deploytoagents.com. Marketplaces we read that list it: 1 (Official MCP Registry). Tuning Engines - Governed AI Runtime is an MCP server published by cerebrixos-org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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 |  Deploy to Agents |  Tuning Engines - Governed AI Runtime |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
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 |
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 | Deploy to Agents | Tuning Engines - Governed AI Runtime |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | 6 (last published figure) |
| Forks (GitHub) (differs) | 0 | 4 (last published figure) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (deploytoagents.com/mcp) | On your machine (tuningengines-cli) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/saezbaldo/deploytoagents | github.com/cerebrixos-org/tuning-engines-cli |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 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
Deploy to Agents
Audit agent-distribution surfaces and create an evidence-based distribution plan.
Tuning Engines - Governed AI Runtime
Govern model, agent, skill, and MCP workflows with policy, approvals, traces, and usage analytics.
How to run each
Deploy to Agents As a remote MCP server
claude mcp add --transport http deploy-to-agents https://deploytoagents.com/mcpTuning Engines - Governed AI Runtime As a local MCP server: npm package
claude mcp add --env "TE_API_KEY=<YOUR_TE_API_KEY>" --transport stdio tuning-engines -- npx -y tuningengines-cli mcp serveRequires: TE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Deploy to Agents 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
The marketplaces of Deploy to Agents publish no settings it asks for, so we do not compare settings.
What it can do: Deploy to Agents · What it can do: Tuning Engines - Governed AI Runtime · 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.