@hanzo/mcp vs @mcpfusion/core
@hanzo/mcp is an MCP server published by @hanzo. Marketplaces we read that list it: 2 (npm registry (MCP servers), PyPI (MCP servers)). @mcpfusion/core is an MCP server published by @mcpfusion. Marketplaces we read that list it: 1 (npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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 |  @hanzo/mcp | |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 2.4.22 Downloads/month (npm): 1 263 Downloads/week (npm): 111 Forks (GitHub): 12 Stars (GitHub): 9 Not marked · First seen |
Listed Version: 5.1.0 Downloads/month (npm): 4 777 Downloads/week (npm): 854 Forks (GitHub): 24 Stars (GitHub): 255 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 0.15.21 Downloads/month (PyPI): 759 Downloads/week (PyPI): 106 Forks (GitHub): 12 Stars (GitHub): 9 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 | @hanzo/mcp | @mcpfusion/core |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 9 (worse) | 255 (better) |
| Forks (GitHub) (differs) | 12 (worse) | 24 (better) |
| Last release (differs) | 2026-11-02 | Not published |
| Where it runs (differs) | On your machine (@hanzo/mcp) | On your machine (@mcpfusion/core) |
| Transport | Not stated | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/hanzoai/mcp | github.com/vinkius-labs/mcpfusion |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen | 2026-10-12 | 2026-10-12 |
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
@hanzo/mcp
Hanzo MCP Server - Unified tool surface with AI, cloud control, vector search, and multi-framework UI
@mcpfusion/core
MVA (Model-View-Agent) framework for the Model Context Protocol. Structured perception packages with Presenters, cognitive guardrails, self-healing errors, action consolidation, and tRPC-style type safety — so AI agents perceive and act on your data det
How to run each
@hanzo/mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
@mcpfusion/core
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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
Neither one's marketplaces publish the settings it asks for.
What it can do: @hanzo/mcp · What it can do: @mcpfusion/core · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.