SDD Vault vs io.github.CloudCorpRecords/specforge
SDD Vault is an MCP server published by sddvault.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.CloudCorpRecords/specforge is an MCP server published by CloudCorpRecords. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
| Marketplace |  io.github.CloudCorpRecords/specforge | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.0 No figure published Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | SDD Vault | io.github.CloudCorpRecords/specforge |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | 2026-11-09 | Not published |
| Where it runs (differs) | Not stated | On your machine (@reneturcios/specforge) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/cloudcorprecords/specforge |
| Changes in the last 7 days (differs) | 4 | 2 |
| First seen (differs) | 2026-11-06 | 2026-11-02 |
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
SDD Vault
Spec Driven Development store: constitution, specs, plans and tasks your agents read and write.
io.github.CloudCorpRecords/specforge
Spec-driven development locally: specs, constitutions, plans, tasks, git and quality checks.
How to run each
SDD Vault
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.CloudCorpRecords/specforge As a local MCP server: npm package
claude mcp add --transport stdio specforge -- npx -y @reneturcios/specforge mcpCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: SDD Vault · What it can do: io.github.CloudCorpRecords/specforge · Compare two other plugins
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.