Ext Ops Panel
Open dashboard
Comparison

Plugged.in Proxy vs Assurance

Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). Assurance is an MCP server published by i-ops-hq. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-29. 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
MarketplacePlugged.in ProxyAssurance
Docker MCP Catalog Listed
Version: sha256:b7c32590b270
Forks (GitHub): 30
Pulls (Docker Hub): 36 220
Stars (Docker Hub): 3
Stars (GitHub): 138
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.5.10
Downloads/month (PyPI): 2 868
Downloads/week (PyPI): 182
Forks (GitHub): 3
Stars (GitHub): 7
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.5.10
Downloads/month (PyPI): 2 868
Downloads/week (PyPI): 182
Forks (GitHub): 3
Stars (GitHub): 7
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

Plugged.in Proxy vs Assurance
FactPlugged.in ProxyAssurance
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)138 (better)7 (worse)
Pulls (Docker Hub) (differs)36 220No figure on Docker Hub
Forks (GitHub) (differs)30 (better)3 (worse)
Last release (differs)Not published2026-10-28
Where it runs (differs)On your machine (mcp/pluggedin-mcp-proxy)On your machine (assurance-mcp)
Transportstdiostdio
Tools it declares (differs)6Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/veriteknik/pluggedin-mcp-proxygithub.com/i-ops-hq/assurance
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11

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.

Assurance

In its own words, on Official MCP Registry:

Checks what an agent did NOT read. Coverage over a retrieval step or a folder.

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)

Assurance As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio assurance-mcp -- uvx assurance-mcp

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

Tools each declares

The marketplaces of Assurance publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Assurance publish no settings it asks for, so we do not compare settings.

What it can do: Plugged.in Proxy · What it can do: Assurance · 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. Package data comes from the Python Package Index (pypi.org). 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