Ext Ops Panel
Open dashboard
Comparison

tdd-guard vs Noosphere

tdd-guard is a plugin bundle for AI coding tools published by nizos. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-20. 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
Marketplacetdd-guardNoosphere
Claude Code: claude-plugins-community Listed
Version: 1.3.0
Forks (GitHub): 190
Stars (GitHub): 2 363
Not marked · First seen
Listed
Version: 0.10.0
Forks (GitHub): 3
Stars (GitHub): 18
Not marked · First seen
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

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

tdd-guard vs Noosphere
Facttdd-guardNoosphere
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)2 363 (better)18 (worse)
Forks (GitHub) (differs)190 (better)3 (worse)
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)31
Parts of the bundle (differs)45
Licence (differs)MITApache-2.0
Repository (differs)github.com/nizos/tdd-guardgithub.com/jinning6/noosphere
Changes in the last 7 days00
First seen (differs)2026-10-122026-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

tdd-guard

In its own words, on Claude Code: claude-plugins-community:

Enforces Test-Driven Development by intercepting file operations in Claude Code. When Claude attempts to edit or write files, TDD Guard validates the changes against TDD principles — blocking operations that skip tests or over-implement, and explaining what needs to happen instead.

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

tdd-guard As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install tdd-guard@claude-community

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 tdd-guard publish no settings it asks for, so we do not compare settings.

What it can do: tdd-guard · What it can do: Noosphere · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.

Where the data comes from: how the catalog is built