OpenMesh vs DomainKits
OpenMesh is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). DomainKits is an MCP server published by ABTdomain. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 |  OpenMesh |  DomainKits |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.3.2 Downloads/month (npm): 536 Downloads/week (npm): 69 Forks (GitHub): 1 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
| Fact | OpenMesh | DomainKits |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 7 |
| Forks (GitHub) (differs) | No figure on GitHub | 1 |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | Remote server (api.openmesh.dev/mcp) | Remote server (api.domainkits.com/v1/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares (differs) | 4 | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/abtdomain/domainkits-mcp |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-13 | Responded 5 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
OpenMesh
Discover and connect to a curated marketplace of MCP servers for extending AI agent capabilities.
DomainKits
Search newly registered, expired, aged, active, deleted and for-sale domains, plus WHOIS and DNS.
How to run each
OpenMesh As a remote MCP server
claude mcp add --transport http openmesh https://api.openmesh.dev/mcpDomainKits As a remote MCP server
claude mcp add --transport http domainkits-mcp https://api.domainkits.com/v1/mcpRequires: DOMAINKITS_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of DomainKits responded at the last daily check. How we check endpoints
Tools each declares
Only OpenMesh has
call_servicediscover_serviceget_alternativereport_experience
Only DomainKits has
activeagedavailablebacklink_summarybulk_availablebulk_tlddeleteddnsdomain_changesepp_statusexpiredip_lookup
Show the remaining 18
keyword_datakeywords_trendsmarketmarket_pricemonitornrdsns_reversepreferencespriceregistrarstrategytld_checktld_ranktld_trendstyposquatunregistered_short_domainsusagewhois
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (DomainKits as of 2026-10-14). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of OpenMesh publish no settings it asks for, so we do not compare settings.
What it can do: OpenMesh · What it can do: DomainKits · 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.