Ext Ops Panel
Open dashboard
Comparison

Close vs io.github.unempyd/revenueos

Close is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.unempyd/revenueos is an MCP server published by unempyd. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-17. 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
MarketplaceCloseio.github.unempyd/revenueos
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.4
Downloads/month (PyPI): 1 127
Downloads/week (PyPI): 28
Forks (GitHub): 0
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

Close vs io.github.unempyd/revenueos
FactCloseio.github.unempyd/revenueos
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub7
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.close.com/mcp)On your machine (revenueos)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 1
Parts of the bundle (differs)Not a bundle7
Licence (differs)Apache-2.0MIT
Repository (differs)Not statedgithub.com/unempyd/revenueos
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 22 h ago, requires a keyno remote endpoint we check

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

Close

In its own words, on Docker MCP Catalog:

Streamline sales processes with integrated calling, email, SMS, and automated workflows for small and scaling businesses.

io.github.unempyd/revenueos

In its own words, on Official MCP Registry:

Self-hosted revenue department: find opportunities, execute approved work, measure results.

How to run each

Close As a remote MCP server

Claude Code
claude mcp add --transport http close https://mcp.close.com/mcp

Requires: CLOSE_API_KEY (secret)

io.github.unempyd/revenueos As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --transport stdio revenueos -- uvx revenueos revenueos-mcp

Requires: ANTHROPIC_API_KEY (secret)

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

Only Close 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

Only Close asks for

  • CLOSE_API_KEY (secret)

Only io.github.unempyd/revenueos asks for

  • ANTHROPIC_API_KEY (secret)
  • REVENUEOS_ROOT

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

What it can do: Close · What it can do: io.github.unempyd/revenueos · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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