Homespun vs Gnosis MCP
Homespun is an MCP server published by homespun.dev. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Gnosis MCP is an MCP server published by nicholasglazer. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, PyPI (MCP servers)). As of our marketplace pass on 2026-11-11. 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 |  Homespun |  Gnosis MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 1.6.98 Downloads/month (npm): 1 794 Downloads/week (npm): 84 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.17.5 Downloads/month (PyPI): 1 440 Downloads/week (PyPI): 159 Forks (GitHub): 11 Stars (GitHub): 31 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 1.6.99 Downloads/month (npm): 1 794 Downloads/week (npm): 84 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.13.3 Forks (GitHub): 11 Stars (GitHub): 31 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.17.5 Downloads/month (PyPI): 1 440 Downloads/week (PyPI): 159 Forks (GitHub): 11 Stars (GitHub): 31 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 | Homespun | Gnosis MCP |
|---|---|---|
| Marketplaces that list it (differs) | 2 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 1 (worse) | 31 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 11 (better) |
| Last release (differs) | 2026-10-20 | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (gnosis-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 2 | Not published |
| Hooks it runs (differs) | Not published | 1 |
| Parts of the bundle (differs) | Not a bundle | 15 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/homespunapps/homespun | github.com/nicholasglazer/gnosis-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 21 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
Homespun
Deploy a multi-user web app from your agent: hosting, auth, database, and permissions.
Gnosis MCP
Zero-config MCP server for searchable documentation. SQLite or PostgreSQL.
How to run each
Homespun As a remote MCP server
claude mcp add --transport http homespun https://homespun.dev/mcpRequires: HOMESPUN_API_KEY (secret), HOMESPUN_REGISTER_SECRET (secret)
Gnosis MCP As a local MCP server: PyPI package
claude mcp add --transport stdio gnosis -- uvx gnosis-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Homespun has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of Gnosis MCP nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of Gnosis MCP publish no settings it asks for, so we do not compare settings.
What it can do: Homespun · What it can do: Gnosis MCP · 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 the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.