Contentrain vs io.weavz/weavz
Contentrain is an MCP server published by Contentrain. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). io.weavz/weavz is an MCP server published by weavz.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  Contentrain |  io.weavz/weavz |
|---|---|---|
| Official MCP Registry | Listed Version: 3.11.16 Downloads/month (npm): 13 422 Downloads/week (npm): 1 470 Forks (GitHub): 0 Stars (GitHub): 6 Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 3.11.16 Downloads/month (npm): 13 422 Downloads/week (npm): 1 470 Forks (GitHub): 0 Stars (GitHub): 6 Not marked · First seen |
Not listed |
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 | Contentrain | io.weavz/weavz |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 6 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-10-24 | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (platform.weavz.io/mcp/weavz) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/contentrain/ai | Not stated |
| Changes in the last 7 days (differs) | 20 or more | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | Answered with HTTP 404 (6 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
Contentrain
Git-native content governance for AI agents — 27 deterministic MCP tools over stdio and HTTP.
io.weavz/weavz
Governed app access for AI agents: 1,000+ apps & 12,000+ tools via Code Mode MCP.
How to run each
Contentrain As a remote MCP server
claude mcp add --transport http contentrain https://studio.contentrain.io/api/mcp/remoteio.weavz/weavz As a remote MCP server
claude mcp add --transport http weavz https://platform.weavz.io/mcp/weavzCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.weavz/weavz 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: Contentrain · What it can do: io.weavz/weavz · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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.