# bug2context (pypi · bug2context)

Turn bug screen recordings into chronological context for AI agents: frames, OCR, logcat, voice.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `bug2context`: 84/100 (this document), [markdown](https://verifymcp.io/servers/emanueld92-bug2context/bug2context.md), [page](https://verifymcp.io/servers/emanueld92-bug2context/bug2context)

## Channel facts

- Registry: `pypi`
- Package: `bug2context`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 4 of 41 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to emanueld92/bug2context).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 14 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 275 tokens (~91/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (67% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add emanueld92-bug2context -- uvx bug2context
```

### Cursor

```json
{
  "mcpServers": {
    "emanueld92-bug2context": {
      "command": "uvx",
      "args": [
        "bug2context"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "emanueld92-bug2context": {
      "command": "uvx",
      "args": [
        "bug2context"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add emanueld92-bug2context -- uvx bug2context
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "emanueld92-bug2context": {
      "type": "local",
      "command": [
        "uvx",
        "bug2context"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add emanueld92-bug2context --command uvx --arg bug2context
```

### Hermes

```yaml
mcp_servers:
  emanueld92-bug2context:
    command: "uvx"
    args: ["bug2context"]
```

### Netclaw

```json
{
  "McpServers": {
    "emanueld92-bug2context": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "bug2context"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add emanueld92-bug2context -t stdio -c uvx -a bug2context
```

### Other

```json
{
  "mcpServers": {
    "emanueld92-bug2context": {
      "command": "uvx",
      "args": [
        "bug2context"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 84, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-04 (score 68, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-03 (score 83, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-02 (score 82, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-01 (score 82, +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.

### 2026-10-29 (score 81, +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.

### 2026-10-27 (score 80, +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.

### 2026-10-25 (score 79, +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.

## MCP tools (3)

### `analyze_bug_video` (~148 tokens)

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.

Input parameters:

- `max_frames`
- `ocr` (boolean)
- `transcribe_audio` (boolean)
- `video_path` (string, required)
- `workdir` (string)

Output parameters:

- `result` (string)

### `get_frame` (~57 tokens)

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).

Input parameters:

- `bundle_path` (string, required)
- `frame_index` (integer, required)

### `list_bundles` (~26 tokens)

List previously processed bundles, newest first.

Input parameters:

- `workdir` (string)

Output parameters:

- `result` (array)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/emanueld92-bug2context/bug2context#diagnostics

## Score history

- 2026-11-05: 84
- 2026-11-04: 68
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 81
- 2026-10-28: 80
- 2026-10-27: 80
- 2026-10-26: 79
- 2026-10-25: 79
- 2026-10-24: 78
- 2026-10-23: 78
- 2026-10-22: 77
- 2026-10-21: 77

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/bug2context/
- Socket report: https://socket.dev/pypi/package/bug2context
- Repository: https://github.com/emanueld92/bug2context
- Changelog RSS feed: https://verifymcp.io/servers/emanueld92-bug2context/bug2context.xml
- Changelog JSON feed: https://verifymcp.io/servers/emanueld92-bug2context/bug2context.json
- HTML version of this page: https://verifymcp.io/servers/emanueld92-bug2context/bug2context