Pitroom
NPM · PITROOM
Hands bounded coding work to cheaper worker agents: verified answers, exact diffs, cost receipts.
Available components
Last scanned (16 hours ago)
Scores higher than 93% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to ATASTECH/pitroom). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1594 tokens (~159/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 65% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 0
- Stability: 0.50 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.27.0 → 0.29.0 functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
- Stability: 0.37 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.25.0 → 0.27.0 functional
- Package version: 0.25.0 → 0.26.0 functional
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/pitroom@0.29.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | ATASTECH/pitroom |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ATASTECH/pitroom/.github/workflows/release.yml@refs/tags/v0.29.0 |
| Rekor log index | 3565665813 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a45921c93c681a51bd428cfd0acf69f4048369f38f7084f3325ecaf31ae9898710f3098550f1d6cee9bbf694cb90be2f6726bbcd42196dddd0a83f4a9 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
pitroom_apply Apply an isolated change ~79
Land an isolated run's patch (or a group's, in order) on the working tree; checked first. A patch deleting files needs allowDelete: pass it only after checking the deletions were asked for.
| Name | Type | Req | Description |
|---|---|---|---|
| allowDelete | boolean | – | – |
| group | string | – | – |
| run | string | – | Run id, or "last". |
No output schema declared.
No examples provided.
pitroom_audit Audit an answer ~98
Another worker re-checks a read run's answer: AGREE, PARTIAL or DISAGREE, with the disputed claims.
| Name | Type | Req | Description |
|---|---|---|---|
| run | string | yes | Run id, or "last". |
| waitSeconds | number | – | Seconds before returning "still running" (default 50, max 540). |
| worker | string | – | Worker "backend[:model]", e.g. "opencode", "claude:haiku". |
No output schema declared.
No examples provided.
pitroom_discard Discard an isolated change ~36
Drop an isolated run's private copy (the patch is kept).
| Name | Type | Req | Description |
|---|---|---|---|
| run | string | yes | Run id, or "last". |
No output schema declared.
No examples provided.
pitroom_info Pitroom information ~213
Reports, changing nothing. topic: runs (latest runs; running, group), history (search earlier answers before asking again; text, state, model, since, limit), stats (success rate, time, tokens, audits per worker; since), savings (since, perModel), models (a backend's models and costs; worker, all), prices (USD per 1M tokens: the primary the savings are measured against, and each worker in use or the one named; worker), cooldown (rate-limited models being skipped), config, doctor (setup check).
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | – |
| group | string | – | – |
| limit | number | – | – |
| model | string | – | – |
| perModel | boolean | – | – |
| running | boolean | – | – |
| since | string | – | 7d, 30d, … or all. |
| state | string | – | – |
| text | string | – | – |
| topic | string | yes | – |
| worker | string | – | – |
No output schema declared.
No examples provided.
pitroom_revert Undo an in-place change ~41
Undo a mode "write" run's changes (refused if the files changed since).
| Name | Type | Req | Description |
|---|---|---|---|
| run | string | yes | Run id, or "last". |
No output schema declared.
No examples provided.
pitroom_review Review a change ~179
A read-only reviewer (another worker by default) judges a run's change or a commit range ("main..HEAD"): findings with severities and a SPEC / QUALITY verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Project directory (default: the server's). |
| group | string | – | Group name for related runs. |
| plan | string | – | With range: the plan file it implements. |
| range | string | – | Or a commit range "A..B". |
| run | string | – | Run id, or "last". |
| tier | string | – | cheap, standard or capable (from the config). |
| waitSeconds | number | – | Seconds before returning "still running" (default 50, max 540). |
| worker | string | – | Worker "backend[:model]", e.g. "opencode", "claude:haiku". |
No output schema declared.
No examples provided.
pitroom_run Run a worker ~488
Hand a bounded task to a cheaper worker agent. mode "read" (default): read-only research, an answer with verified file:line references. "isolate": the worker edits a private copy and you get the exact diff (then pitroom_review, pitroom_apply or pitroom_discard). "write": edits the working tree (undo: pitroom_revert). "tasks" or "scopes" run workers in parallel (read or isolate). Returns the report(s) and a receipt (a read question asked before on the same code comes back cached), or "still running" for pitroom_wait. The using-pitroom skill (or prompt) says when and how to delegate. Cancelling the call stops the run.
| Name | Type | Req | Description |
|---|---|---|---|
| audit | boolean | – | Read: have another worker re-check the answer (each one, with tasks). |
| continue | string | – | A finished run to follow up in the same worker session. |
| dir | string | – | Project directory (default: the server's). |
| effort | string | – | low, medium, high, xhigh. |
| files | array | – | Files to attach. |
| fresh | boolean | – | Read: ask a worker even if this question was answered on the same code. |
| group | string | – | Group name for related runs. |
| inPlace | boolean | – | Read: read the directory itself, not a snapshot without secret-looking files. |
| link | array | – | Ignored dirs to link into an isolated copy, e.g. ["node_modules"]. |
| mode | string | – | – |
| model | string | – | Model for that worker. |
| scopes | array | – | Or "task" per part ({scope}): paths that do not overlap, or "src/*/". |
| task | string | – | What to do, with the context the worker needs. |
| tasks | array | – | Or independent tasks, one worker each. |
| tier | string | – | cheap, standard or capable (from the config). |
| verify | string | – | Command run afterwards, e.g. "npm test". |
| waitSeconds | number | – | Seconds before returning "still running" (default 50, max 540). |
| web | boolean | – | Allow web tools. |
| worker | string | – | Worker "backend[:model]", e.g. "opencode", "claude:haiku". |
No output schema declared.
No examples provided.
pitroom_show Show a run ~61
A run's report (live progress while it runs); patch: the exact diff; full: the untruncated answer.
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | – | – |
| patch | boolean | – | – |
| run | string | – | Run id, or "last". |
No output schema declared.
No examples provided.
pitroom_stop Stop runs ~59
Stop a running or queued run, or a group; cooldowns: try rate-limited models again now.
| Name | Type | Req | Description |
|---|---|---|---|
| cooldowns | boolean | – | – |
| group | string | – | – |
| run | string | – | Run id, or "last". |
No output schema declared.
No examples provided.
pitroom_wait Wait for runs ~61
Wait for runs that came back "still running" and return their reports.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | – |
| runs | array | – | – |
| waitSeconds | number | – | Seconds before returning "still running" (default 50, max 540). |
No output schema declared.
No examples provided.
How do I install the Pitroom MCP server?
Pitroom runs locally as an npm package, launched with npx -y pitroom mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · pitroom
claude mcp add atastech-pitroom -- npx -y pitroom mcp
What is the Pitroom MCP server?
Pitroom is an MCP server listed in the public MCP registry as io.github.ATASTECH/pitroom. Hands bounded coding work to cheaper worker agents: verified answers, exact diffs, cost receipts. This page covers its npm package (pitroom).
Is the Pitroom MCP server safe to use?
Pitroom scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Pitroom MCP server expose?
Pitroom exposes 10 tools: pitroom_run, pitroom_wait, pitroom_show, pitroom_info, pitroom_review, and 5 more. Their descriptions and schemas cost roughly 1,315 tokens of context every time the server is loaded.
Is the Pitroom MCP server still maintained?
Pitroom is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Pitroom MCP server under?
Pitroom declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Pitroom MCP server?
VerifyMCP ran 16 checks on Pitroom, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.