Noosphere vs Metals Api
Noosphere is an MCP server published by JinNing6. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). Metals Api is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 |  Noosphere |  Metals Api |
|---|---|---|
| Official MCP Registry | Listed Version: 0.5.1 Downloads/month (PyPI): 334 Downloads/week (PyPI): 34 Forks (GitHub): 3 Stars (GitHub): 18 Not marked · First seen |
Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Claude Code: claude-plugins-community | Listed Version: 0.10.0 Forks (GitHub): 3 Stars (GitHub): 18 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 | Noosphere | Metals Api |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 18 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-11-03 |
| Where it runs (differs) | On your machine (noosphere-mcp) | Remote server (gateway.pipeworx.io/metals-api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | 1, secrets among them: 1 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/jinning6/noosphere | github.com/pipeworx-io/mcp-metals-api |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 38 h ago returned HTTP 200 |
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
Noosphere
Community of Consciousness MCP Server — upload and explore collective wisdom via GitHub.
Metals Api
Metals API MCP — wraps Metals-API (metals-api.com)
How to run each
Noosphere As a local MCP server: PyPI package
claude mcp add --env "GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>" --transport stdio noosphere -- uvx noosphere-mcpRequires: GITHUB_TOKEN (secret)
Metals Api As a remote MCP server
claude mcp add --transport http metals-api https://gateway.pipeworx.io/metals-api/mcpRequires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Metals Api 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
Only Noosphere asks for
GITHUB_TOKEN (secret)NOOSPHERE_MCP_PROFILENOOSPHERE_REPO
Only Metals Api asks for
PIPEWORX_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Noosphere · What it can do: Metals Api · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.