io.github.RohitYajee8076/backburner
PYPI · BACKBURNER-MCP
Run long shell commands as background tasks: start them, keep working, collect the results later
Available components
Last scanned (9 hours ago)
Scores higher than 76% of PyPI 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
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 94 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 355 tokens (~71/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (20% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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 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.
- 4 Nov 26 −5
- Stability: pass → 0.67 functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.80 functional
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 pypi/backburner-mcp@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| 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 →
cancel_task ~27
Cancel a running task, killing its whole process tree.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | – |
No output schema declared.
No examples provided.
list_tasks ~22
List recent tasks, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
start_task ~140
Start a shell command as a background task and return immediately. Args: command: The shell command to run (e.g. "pytest -q" or "npm run build"). cwd: Working directory for the command. Defaults to the server's cwd. timeout_seconds: If set, the task is killed and marked 'timed_out' when it runs longer than this. Recommended for unattended jobs. Returns the new task's id and initial status. The command keeps running after this call returns — use task_status / task_result to follow it.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | – |
| cwd | – | – | – |
| timeout_seconds | – | – | – |
No output schema declared.
No examples provided.
task_result ~78
Get a task's captured output (stdout+stderr merged). Args: task_id: The task to inspect. Works for finished AND still-running tasks, so you can peek at live progress. tail_lines: How many trailing lines of output to return.
| Name | Type | Req | Description |
|---|---|---|---|
| tail_lines | integer | – | – |
| task_id | string | yes | – |
No output schema declared.
No examples provided.
task_status ~35
Check on a task: working, completed, failed, cancelled, timed_out, or interrupted.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.RohitYajee8076/backburner MCP server?
io.github.RohitYajee8076/backburner runs locally as a PyPI package, launched with uvx backburner-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · backburner-mcp
claude mcp add rohityajee8076-backburner -- uvx backburner-mcp
What is the io.github.RohitYajee8076/backburner MCP server?
io.github.RohitYajee8076/backburner is an MCP server listed in the public MCP registry as io.github.RohitYajee8076/backburner. Run long shell commands as background tasks: start them, keep working, collect the results later. This page covers its PyPI package (backburner-mcp).
Is the io.github.RohitYajee8076/backburner MCP server safe to use?
io.github.RohitYajee8076/backburner scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 io.github.RohitYajee8076/backburner MCP server expose?
io.github.RohitYajee8076/backburner exposes 5 tools: start_task, task_status, task_result, cancel_task, list_tasks. Their descriptions and schemas cost roughly 302 tokens of context every time the server is loaded.
Is the io.github.RohitYajee8076/backburner MCP server still maintained?
io.github.RohitYajee8076/backburner 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 io.github.RohitYajee8076/backburner MCP server under?
io.github.RohitYajee8076/backburner declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.