Close vs Versium REACH
Close is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Versium REACH is an MCP server published by versium.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
| Marketplace |  Close | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published 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
| Fact | Close | Versium REACH |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.close.com/mcp) | Remote server (app.versium.com/mcp/reach) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository | Not stated | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | Responded less than an hour 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
Close
Streamline sales processes with integrated calling, email, SMS, and automated workflows for small and scaling businesses.
Versium REACH
Enrich leads, generate prospect lists, and validate emails using Versium's B2B2C identity graph.
How to run each
Close As a remote MCP server
claude mcp add --transport http close https://mcp.close.com/mcpRequires: CLOSE_API_KEY (secret)
Versium REACH As a remote MCP server
claude mcp add --transport http reach https://app.versium.com/mcp/reachCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Versium REACH 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
The marketplaces of Versium REACH publish no settings it asks for, so we do not compare settings.
What it can do: Close · What it can do: Versium REACH · 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 . We publish no contact details for plugin publishers.