Clawhard Studio vs io.github.zeroclaw-labs/zeroclaw-mcp
Clawhard Studio is an MCP server published by clawhard.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.zeroclaw-labs/zeroclaw-mcp is an MCP server published by zeroclaw-labs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. 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 |  Clawhard Studio |  io.github.zeroclaw-labs/zeroclaw-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 1.17.0 No figure published Not marked · First seen |
Listed Version: 0.1.0-alpha.4 Downloads/month (npm): 815 Downloads/week (npm): 332 Forks (GitHub): 0 Stars (GitHub): 0 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 | Clawhard Studio | io.github.zeroclaw-labs/zeroclaw-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | 2026-11-13 | Not published |
| Where it runs (differs) | Remote server (mcp.clawhard.com/mcp) | On your machine (@zeroclaw-labs/zeroclaw-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/zeroclaw-labs/zeroclaw-mcp-distribution |
| Changes in the last 7 days (differs) | 8 | 0 |
| First seen (differs) | 2026-10-28 | 2026-10-24 |
| Endpoint at the last check (differs) | Responded 4 h ago | no 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
Clawhard Studio
Token counts, contrast, time zones, cron, JSON repair, DMARC, packages, Unicode, links, quotes
io.github.zeroclaw-labs/zeroclaw-mcp
Configure and manage authorized ZeroClaw installations through a local MCP server.
How to run each
Clawhard Studio As a remote MCP server
claude mcp add --transport http studio https://mcp.clawhard.com/mcpio.github.zeroclaw-labs/zeroclaw-mcp As a local MCP server: npm package
claude mcp add --transport stdio zeroclaw-mcp -- npx -y @zeroclaw-labs/zeroclaw-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Clawhard Studio 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
Neither one's marketplaces publish the settings it asks for.
What it can do: Clawhard Studio · What it can do: io.github.zeroclaw-labs/zeroclaw-mcp · Compare two other plugins
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.