Ext Ops Panel
Open dashboard
Comparison

refinery vs Noosphere

refinery is a plugin bundle for AI coding tools published by binref. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Noosphere is an MCP server published by JinNing6. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-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

Where each is published
MarketplacerefineryNoosphere
Community marketplace binref/agent Listed
Version: 0.0.15
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.5.1
Downloads/month (PyPI): 334
Downloads/week (PyPI): 104
Forks (GitHub): 3
Stars (GitHub): 18
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.10.0
Forks (GitHub): 3
Stars (GitHub): 18
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

refinery vs Noosphere
FactrefineryNoosphere
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)No figure on GitHub18
Forks (GitHub) (differs)No figure on GitHub3
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (noosphere-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Hooks it runs (differs)Not published1
Parts of the bundle (differs)15
Licence (differs)BSD-3-ClauseApache-2.0
Repository (differs)github.com/binref/agentgithub.com/jinning6/noosphere
Changes in the last 7 days22
First seen (differs)2026-10-142026-10-11

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

refinery

In its own words, on Community GitHub marketplaces:

Binary Refinery skill for binary data transformations & conversions. Vast library of decoding, decompression, unpacking, and decryption utilities. Useful for malware analysis or other reverse engineering tasks.

Noosphere

In its own words, on Official MCP Registry:

Community of Consciousness MCP Server — upload and explore collective wisdom via GitHub.

How to run each

refinery As a Claude Code plugin

Claude Code
/plugin marketplace add binref/agent
/plugin install refinery@binref

Noosphere As a local MCP server: PyPI package

Claude Code
claude mcp add --env "GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>" --transport stdio noosphere -- uvx noosphere-mcp

Requires: GITHUB_TOKEN (secret)

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

The marketplaces of refinery publish no settings it asks for, so we do not compare settings.

What it can do: refinery · What it can do: Noosphere · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built