Sequa.AI vs sp-ecc
sp-ecc is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑27.
Sequa.AI is an MCP server published by sequa-ai. Marketplaces we read that list it: 1 (Docker MCP Catalog). sp-ecc is a plugin bundle for AI coding tools published by Faisal Alqarni. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-27. 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 |  Sequa.AI | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:f4e0e271c5c5 Forks (GitHub): 5 Pulls (Docker Hub): 10 679 Stars (Docker Hub): 1 Stars (GitHub): 22 Not marked · First seen |
Not listed |
| Community marketplace faisalalqarni/sp-ecc | Not listed | Removed on 2026-10-27 Version: 1.3 Forks (GitHub): 3 Stars (GitHub): 11 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 | Sequa.AI | sp-eccno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 22 | 11 |
| Pulls (Docker Hub) (differs) | 10 679 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 5 | 3 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/sequa) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Hooks it runs (differs) | Not published | 17 |
| Parts of the bundle (differs) | Not a bundle | 107 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/sequa-ai/sequa-mcp | github.com/faisalalqarni/sp-ecc |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-18 |
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 sp-ecc
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Senior craftsman methodology for Claude Code. 22 commands, 12 specialized agents, and automated hooks that enforce DDD, Clean Architecture, and TDD practices. Includes 3-level…
-
Superpowers teaches Claude brainstorming, subagent driven development with built in code review, systematic debugging, and red/green TDD. Additionally, it teaches Claude how to…
-
Evidence-first Claude Code plugin for repeatable, spec-driven development workflows.
-
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
-
Personal Claude Code configuration with 14 productivity commands and 11 specialized AI agents for modern web development
-
Planning and execution workflows for Claude Code. Based on obra/superpowers.
What each says it does
Sequa.AI
Stop stitching context for Copilot and Cursor. With Sequa MCP, your AI tools know your entire codebase and docs out of the box.
sp-ecc
Integration of Superpowers and Everything Claude Code
How to run each
Sequa.AI As a local MCP server: Docker image
claude mcp add --env "API_KEY=<YOUR_API_KEY>" --transport stdio sequa -- docker run -i --rm -e API_KEY mcp/sequaRequires: API_KEY (secret)
sp-ecc
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of sp-ecc publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of sp-ecc publish no settings it asks for, so we do not compare settings.
What it can do: Sequa.AI · What it can do: sp-ecc · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.