pair-pipeline vs Brain Scanner
pair-pipeline is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑21.
pair-pipeline is a plugin bundle for AI coding tools published by Pair Pipeline Contributors. No marketplace we read lists it any more. Brain Scanner is an MCP server published by kevin-lozada-santos. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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 |  Brain Scanner | |
|---|---|---|
| Community marketplace gantisstorm/claude-code-pair-planning-framework | Removed on 2026-10-21 Version: 1.7.0 Forks (GitHub): 1 Stars (GitHub): 6 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.8.3 No figure published 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 | pair-pipelineno longer listed · | Brain Scanner |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 6 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-17 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (brainscanner.dev/mcp/v2) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 7 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/gantisstorm/claude-code-pair-planning-framework | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-19 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 15 h ago, requires authentication |
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 pair-pipeline
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Multi-agent orchestration for code analysis, bug investigation, fix planning, and implementation with intelligent routing to specialized agents
-
Multi-agent AI pipelines with structural write/review isolation, crash-safe state recovery, and spec-driven development. Run sequential, parallel fan-out, iterative-loop, or…
-
A multi-agent development framework that splits project builds into phases using three specialized roles: an Orchestrator (plans and coordinates), Workers (implement code), and…
-
Complete AI coding workflow: context engineering, agent teams, 41 skills, 8 agents, 23 commands, 13 guides, cross-agent support, and searchable learnings.
-
Multi-agent orchestration for coding agents: run external agent CLIs (Codex, Claude Code, OpenCode, Grok Build, Gemini, Devin CLI, Antigravity CLI) as independent reviewers…
-
Autonomous overnight coding agent. Queue tasks in YAML, run them via Claude CLI while you sleep, and use self-healing audit-fix loops to hit any quality target. Includes skills…
What each says it does
pair-pipeline
Multi-agent orchestration for complex coding tasks without MCP. Scouts gather raw context, planner synthesizes structured narrative (task, architecture, context, relationships, implementation notes, ambiguities) into per-file instructions. Full discovery loop with user checkpoints and parallel execution.
Brain Scanner
Recover project context, review recorded decisions, and steer queued work across AI coding agents.
How to run each
pair-pipeline
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Brain Scanner As a remote MCP server
claude mcp add --transport http brain-scanner https://brainscanner.dev/mcp/v2Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Brain Scanner 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
Neither one's marketplaces publish the settings it asks for.
What it can do: pair-pipeline · What it can do: Brain Scanner · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.