Comparison

Plugged.in Proxy vs io.github.cyanheads/devops-status-mcp-server

Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.cyanheads/devops-status-mcp-server is an MCP server published by cyanheads. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
Marketplace	Plugged.in Proxy	io.github.cyanheads/devops-status-mcp-server
Docker MCP Catalog	Listed Version: sha256:b7c32590b270 Forks (GitHub): 30 Pulls (Docker Hub): 35 842 Stars (Docker Hub): 3 Stars (GitHub): 136 Not marked · First seen 2026-10-11	Not listed
Official MCP Registry	Not listed	Listed Version: 0.10.0 Downloads/month (npm): 1 281 Downloads/week (npm): 329 Forks (GitHub): 2 Stars (GitHub): 2 Not marked · First seen 2026-10-11

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

Plugged.in Proxy vs io.github.cyanheads/devops-status-mcp-server
Fact	Plugged.in Proxy	io.github.cyanheads/devops-status-mcp-server
Marketplaces that list it	1	1
Stars (GitHub) (differs)	136 (better)	2 (worse)
Pulls (Docker Hub) (differs)	35 842	No figure on Docker Hub
Forks (GitHub) (differs)	30 (better)	2 (worse)
Last release (differs)	Not published	2026-10-14
Where it runs (differs)	On your machine (mcp/pluggedin-mcp-proxy)	Remote server (devops-status.caseyjhand.com/mcp)
Transport (differs)	stdio	Streamable HTTP
Tools it declares (differs)	6	Not published
Environment variables it asks for (differs)	2, secrets among them: 1	8, secrets among them: 0
Licence (differs)	Apache-2.0	Not stated
Repository (differs)	github.com/veriteknik/pluggedin-mcp-proxy	github.com/cyanheads/devops-status-mcp-server
Changes in the last 7 days (differs)	0	1
First seen	2026-10-11	2026-10-11
Endpoint at the last check (differs)	no remote endpoint we check	Responded 2 days 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

Plugged.in Proxy

In its own words, on Docker MCP Catalog:

A unified MCP proxy that aggregates multiple MCP servers into one interface, enabling seamless tool discovery and management across all your AI interactions. Manage all your MCP servers from a single connection point with RAG capabilities and real-time notifications.

io.github.cyanheads/devops-status-mcp-server

In its own words, on Official MCP Registry:

Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.

How to run each

Plugged.in Proxy As a local MCP server: Docker image

Claude Code

claude mcp add --env "PLUGGEDIN_API_KEY=<YOUR_PLUGGEDIN_API_KEY>" --transport stdio pluggedin-mcp-proxy -- docker run -i --rm -e PLUGGEDIN_API_KEY mcp/pluggedin-mcp-proxy

Requires: PLUGGEDIN_API_KEY (secret)

io.github.cyanheads/devops-status-mcp-server As a remote MCP server

Claude Code

claude mcp add --transport http devops-status-mcp-server https://devops-status.caseyjhand.com/mcp

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

Only io.github.cyanheads/devops-status-mcp-server has a remote endpoint we check. How we check endpoints

Tools each declares

Only Plugged.in Proxy has

pluggedin_ask_knowledge_base
pluggedin_delete_notification
pluggedin_discover_tools
pluggedin_list_notifications
pluggedin_mark_notification_done
pluggedin_send_notification

Only io.github.cyanheads/devops-status-mcp-server has

devops_check_certs
devops_check_dns
devops_get_incidents
devops_list_vendors
devops_status_check
devops_suggest_action
devops_watch_stack

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (io.github.cyanheads/devops-status-mcp-server as of 2026-10-16). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only Plugged.in Proxy asks for

PLUGGEDIN_API_BASE_URL
PLUGGEDIN_API_KEY (secret)

Only io.github.cyanheads/devops-status-mcp-server asks for

DEVOPS_STATUS_ALLOW_PRIVATE_TARGETS
DEVOPS_STATUS_DISABLE_ACTIVE_PROBES
MCP_AUTH_MODE
MCP_HTTP_ENDPOINT_PATH
MCP_HTTP_HOST
MCP_HTTP_PORT
MCP_LOG_LEVEL
MCP_TRANSPORT_TYPE

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Plugged.in Proxy · What it can do: io.github.cyanheads/devops-status-mcp-server · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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 2026-10-18. We publish no contact details for plugin publishers.