bug2context
PYPI · BUG2CONTEXT
Turn bug screen recordings into chronological context for AI agents: frames, OCR, logcat, voice.
Available components
Last scanned (47 minutes ago)
Scores higher than 87% of PyPI servers
Category Testing and QA
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
- 4 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to emanueld92/bug2context). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 14 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 275 tokens (~91/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 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 (67% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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 +16
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 pypi/bug2context@0.1.1
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | emanueld92/bug2context |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/emanueld92/bug2context/.github/workflows/release.yml@refs/tags/v0.1.1 |
| Rekor log index | 3361610118 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:0d223da071a1f0060ce150b11e8f49017022ae4210e685f689a51841fd1d2e32 |
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 41 packages
| Packages resolved | 41 |
|---|---|
| Stale | 3 |
| 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 →
analyze_bug_video ~148
Process a bug screen recording into a chronological markdown report. Returns the report itself, so you can reason about it directly. Frames are written next to it and referenced by relative path; use get_frame to view one. Leave max_frames unset unless the report looks too coarse or too long: it is derived from the recording's length. Set transcribe_audio when the recording has someone narrating the bug; it is slow and downloads a model on first use, so it stays off otherwise.
| Name | Type | Req | Description |
|---|---|---|---|
| max_frames | – | – | – |
| ocr | boolean | – | – |
| transcribe_audio | boolean | – | – |
| video_path | string | yes | – |
| workdir | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_frame ~57
Return one frame from a bundle so you can look at it. frame_index is the 1-based number shown in the report (frame_003 -> 3).
| Name | Type | Req | Description |
|---|---|---|---|
| bundle_path | string | yes | – |
| frame_index | integer | yes | – |
No output schema declared.
No examples provided.
list_bundles ~26
List previously processed bundles, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| workdir | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
How do I install the bug2context MCP server?
bug2context runs locally as a PyPI package, launched with uvx bug2context. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · bug2context
claude mcp add emanueld92-bug2context -- uvx bug2context
What is the bug2context MCP server?
bug2context is an MCP server listed in the public MCP registry as io.github.emanueld92/bug2context. Turn bug screen recordings into chronological context for AI agents: frames, OCR, logcat, voice. This page covers its PyPI package (bug2context).
Is the bug2context MCP server safe to use?
bug2context scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 bug2context MCP server expose?
bug2context exposes 3 tools: analyze_bug_video, get_frame, list_bundles. Their descriptions and schemas cost roughly 231 tokens of context every time the server is loaded.
Is the bug2context MCP server still maintained?
bug2context 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 bug2context MCP server under?
bug2context declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.