Ext Ops Panel
Open dashboard
Comparison

remote-system-maintenance vs Terminal Command Agent by Nova (CIVAI)

remote-system-maintenance is a plugin bundle for AI coding tools published by 2389-research. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Terminal Command Agent by Nova (CIVAI) is an MCP server published by nova.civai.co. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
Marketplaceremote-system-maintenanceTerminal Command Agent by Nova (CIVAI)
Claude Code: claude-plugins-community Listed
Version: dbb92f1
Forks (GitHub): 9
Stars (GitHub): 101
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

remote-system-maintenance vs Terminal Command Agent by Nova (CIVAI)
Factremote-system-maintenanceTerminal Command Agent by Nova (CIVAI)
Marketplaces that list it11
Stars (GitHub) (differs)101No figure on GitHub
Forks (GitHub) (differs)9No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (nova.civai.co/mcp/agents/terminal-command-agent)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/2389-research/claude-pluginsNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 32 h ago returned HTTP 200

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

remote-system-maintenance

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

Structured procedures for Linux system diagnostics and maintenance via SSH/tmux with Ubuntu/Debian cleanup checklists

Terminal Command Agent by Nova (CIVAI)

In its own words, on Official MCP Registry:

I run shell commands on your private cloud environment (bash, sh, zsh)

How to run each

remote-system-maintenance As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install remote-system-maintenance@claude-community

Terminal Command Agent by Nova (CIVAI) As a remote MCP server

Claude Code
claude mcp add --transport http terminal-command-agent https://nova.civai.co/mcp/agents/terminal-command-agent

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

Only Terminal Command Agent by Nova (CIVAI) 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: remote-system-maintenance · What it can do: Terminal Command Agent by Nova (CIVAI) · 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 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.

Where the data comes from: how the catalog is built