Warden vs aictrl
aictrl is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
Warden is an MCP server published by Larshiensch99. Marketplaces we read that list it: 1 (Official MCP Registry). aictrl is an MCP server published by vasparshin. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-28. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Removed on 2026-10-18 Version: 1.0.0-beta.1 No figure published 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 | Warden | aictrlno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (warden.flowvolt.io/mcp) | Remote server (aictrl.dev/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/larshiensch99/warden | github.com/vasparshin/aictrl-team-skills |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-17 | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of aictrl
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
dingdawg-governance io.github.dingdawg/dingdawg-governance
Universal governance layer for AI agents. MCP-native, fail-closed, audit proofs and rollback.
-
Context and control for any AI. Agent identity, scoped access, and proof across tools.
-
mcp com.decionis/mcp
Authorize consequential AI agent actions before execution
-
Action-level governance for AI agents -- control what they DO, not what they SAY
-
agentos io.github.imran-siddique/agentos
Build and manage policy-compliant AI agents with safety enforcement and compliance checking
-
aegis-mcp io.github.cleburn/aegis-mcp
Runtime governance enforcement for AI agents. Zero token overhead.
What each says it does
Warden
Register every AI agent, log every action, prove it. EU AI Act compliance built in.
aictrl
Governance layer for AI coding agents: knowledge-graph grounding, session audit, policy controls.
How to run each
Warden As a remote MCP server
claude mcp add --transport http warden https://warden.flowvolt.io/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
aictrl
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Warden 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: Warden · What it can do: aictrl · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.