Ext Ops Panel
Open dashboard
Comparison

vps-ops vs RunStack Checks

vps-ops is a plugin bundle for AI coding tools published by arturseo-geo. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). RunStack Checks is an MCP server published by runstack.pro. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
Marketplacevps-opsRunStack Checks
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 5
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
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

vps-ops vs RunStack Checks
Factvps-opsRunStack Checks
Marketplaces that list it11
Stars (GitHub) (differs)5 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (runstack.pro/api/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)12Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/arturseo-geo/cowork-vps-opsgithub.com/withoutcowards/runstack-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-10-17
Endpoint at the last check (differs)no remote endpoint we checkResponded 7 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

vps-ops

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

Monitor and manage a Linux VPS running WordPress, PM2 services, and Nginx. Checks service health, analyses Nginx logs for AI crawler activity, verifies backups, manages redirects, and runs WordPress site health checks. Includes 6 skills: health-check, log-analysis, backup-check, redirect, site-health, and wp-audit.

RunStack Checks

In its own words, on Official MCP Registry:

External checks of TLS, HTTP headers, email domain, DNS and ports, with cause and fix

How to run each

vps-ops As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install vps-ops@claude-community

RunStack Checks As a remote MCP server

Claude Code
claude mcp add --transport http checks https://runstack.pro/api/mcp --header "X-RunStack-Key: <YOUR_X_RUNSTACK_KEY>"

Requires: X-RunStack-Key header

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

Only RunStack Checks 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: vps-ops · What it can do: RunStack Checks · 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