builder-loop vs Noosphere
builder-loop is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑21.
builder-loop is a plugin bundle for AI coding tools published by Edoardo Spena. No marketplace we read lists it any more. 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-21. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Noosphere | |
|---|---|---|
| Community marketplace edoardospena/builder-loop | Removed on 2026-10-21 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 6 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
| Fact | builder-loopno longer listed · | Noosphere |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 3 |
| Stars (GitHub) (differs) | 6 | 18 |
| Forks (GitHub) (differs) | 0 | 3 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (noosphere-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Hooks it runs (differs) | Not published | 1 |
| Parts of the bundle (differs) | 1 | 5 |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/edoardospena/builder-loop | github.com/jinning6/noosphere |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of builder-loop
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Generate ready-to-paste Claude Code prompts with the right agent, orchestration pattern, and safety rails. Orchestrator synthesises patterns from 6 open-source projects into a…
-
Research-backed orchestration for Claude Code. Structured workflow from idea to production with parallel execution, session memory, 70-point validation, autonomous mode, and…
-
Transform Claude Code into an autonomous AI development powerhouse with persistent task management, intelligent agents, and automatic work discovery
-
Output.ai workflow development toolkit for Claude Code. Adds 5 specialist agents (planner, builder, debugger, prompt writer, quality reviewer), 40+ slash-command skills covering…
-
Intelligent prompt optimization using skill-based architecture. Enriches vague prompts with research-based clarifying questions before Claude Code executes them
-
claude-codex-loop orchestrates a structured collaboration loop between Claude Code (designer/reviewer) and OpenAI Codex (auditor/implementer). It runs two stages — design and code…
What each says it does
builder-loop
Make Claude Code prove it finished the job. Runs a substantial coding task as an evidence-driven closed loop and ends with one explicit ship-or-revise decision.
Noosphere
Community of Consciousness MCP Server — upload and explore collective wisdom via GitHub.
How to run each
builder-loop
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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)
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 builder-loop publish no settings it asks for, so we do not compare settings.
What it can do: builder-loop · 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.