stipulate vs Pitroom
stipulate is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑22.
stipulate is a plugin bundle for AI coding tools published by bryann2k. No marketplace we read lists it any more. Pitroom is an MCP server published by ATASTECH. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-22. 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 |  Pitroom | |
|---|---|---|
| Community marketplace bryann2k/stipulate-skills | Removed on 2026-10-22 Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.25.0 Downloads/month (npm): 5 297 Downloads/week (npm): 1 349 Forks (GitHub): 1 Stars (GitHub): 26 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.25.0 Downloads/month (npm): 5 297 Downloads/week (npm): 1 349 Forks (GitHub): 1 Stars (GitHub): 26 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 | stipulateno longer listed · | Pitroom |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 7 | 26 |
| Forks (GitHub) (differs) | 0 | 1 |
| Last release (differs) | Not published | 2026-10-19 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (pitroom) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/bryann2k/stipulate-skills | github.com/atastech/pitroom |
| Changes in the last 7 days (differs) | 1 | 2 |
| First seen (differs) | 2026-10-14 | 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 stipulate
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Genesis Governance turns a Claude Code project into a governed project. Instead of dropping generic templates, it derives a constitution, governance config, CLAUDE.md, document…
-
Hands for the Stake Engine brain: upload bundles, run compliance checks, publish a release. Needs the stakecli binary.
-
Governance templates that make Claude Code follow your architecture, security rules, and team conventions automatically — across Java, Python, Go, .NET, PHP, and JavaScript stacks.
-
Open-source Claude Code plugins for multi-agent software delivery. Plan-first SDLC workflow, code review, LLM quality judges, and self-learning — grounded in your codebase…
-
Run Claude Code unattended: capped spend, sandboxed execution, signed receipt, enforced from outside the agent's process.
-
Connect Claude Code to Civic for guardrails, scoped permissions, audit trails, and revocable access control. Every tool call is logged, permissions are user-controlled, and access…
What each says it does
stipulate
Stip spec lifecycle in Claude Code: approved-contract workers, ownership guards, approval and apply gates.
Pitroom
Hands bounded coding work to cheaper worker agents: verified answers, exact diffs, cost receipts.
How to run each
stipulate
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Pitroom As a local MCP server: npm package
claude mcp add --transport stdio pitroom -- npx -y pitroom 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: stipulate · What it can do: Pitroom · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.