Close vs Limitguard Lead Verification
Close is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Limitguard Lead Verification is an MCP server published by api.limitguard.ai. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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 |  Limitguard Lead Verification |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.11.4 Forks (GitHub): 0 Stars (GitHub): 1 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 | Limitguard Lead Verification |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-12 |
| Where it runs (differs) | Remote server (mcp.close.com/mcp) | Remote server (api.limitguard.ai/mcp) |
| 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 |
| Parts of the bundle (differs) | Not a bundle | 4 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | Not stated | github.com/jwconsultancyteam/limitguard-mcp |
| Changes in the last 7 days (differs) | 0 | 8 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check | not checked yet | not checked yet |
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.
Limitguard Lead Verification
Lead validation over MCP: KVK/KBO register, EU VAT, sanctions and email checks with sources.
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)
Limitguard Lead Verification As a remote MCP server
claude mcp add --transport http limitguard https://api.limitguard.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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 Limitguard Lead Verification publish no settings it asks for, so we do not compare settings.
What it can do: Close · What it can do: Limitguard Lead Verification · 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.