# mcp-trace-inspector (pypi · mcp-trace-inspector)

Read local agent-run JSONL traces through MCP for failures, approvals, and run comparisons.

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- pypi · `mcp-trace-inspector`: 74/100 (this document), [markdown](https://verifymcp.io/servers/abhishekash-mcp-trace-inspector/mcp-trace-inspector.md), [page](https://verifymcp.io/servers/abhishekash-mcp-trace-inspector/mcp-trace-inspector)

## Channel facts

- Registry: `pypi`
- Package: `mcp-trace-inspector`
- Version: `0.3.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-10-23.

- **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.
  - 1 of 28 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 71/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Cryptographically verified build provenance (signed, bound to abhishekash/mcp-trace-inspector).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 569 tokens (~47/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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 (100% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 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 mcp-trace-inspector server?

mcp-trace-inspector runs locally as a PyPI package, launched with uvx mcp-trace-inspector. 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 abhishekash-mcp-trace-inspector -- uvx mcp-trace-inspector
```

### Cursor

```json
{
  "mcpServers": {
    "abhishekash-mcp-trace-inspector": {
      "command": "uvx",
      "args": [
        "mcp-trace-inspector"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "abhishekash-mcp-trace-inspector": {
      "command": "uvx",
      "args": [
        "mcp-trace-inspector"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add abhishekash-mcp-trace-inspector -- uvx mcp-trace-inspector
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add abhishekash-mcp-trace-inspector --command uvx --arg mcp-trace-inspector
```

### Hermes

```yaml
mcp_servers:
  abhishekash-mcp-trace-inspector:
    command: "uvx"
    args: ["mcp-trace-inspector"]
```

### Netclaw

```json
{
  "McpServers": {
    "abhishekash-mcp-trace-inspector": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcp-trace-inspector"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add abhishekash-mcp-trace-inspector -t stdio -c uvx -a mcp-trace-inspector
```

### Other

```json
{
  "mcpServers": {
    "abhishekash-mcp-trace-inspector": {
      "command": "uvx",
      "args": [
        "mcp-trace-inspector"
      ]
    }
  }
}
```

## 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-10-22 (score 74, +4)

- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Stability: unverified → 0.27

### 2026-10-21 (score 70, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-18 (score 70, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-17 (score 55, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-16 (score 70, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-14 (score 55, +26)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: pass
- [functional] First check of Tool coverage: 100
- [functional] First check of Tool coverage: 0
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: fair
- [functional] First check of Destructive annotations: pass

### 2026-10-13 (score 29)

First indexed and scored.

## MCP tools (12)

### `list_runs` (~45 tokens)

List recent agent runs: task, model, duration, tool use, human decisions, cost.

Use first to find the trace_id for deeper inspection.

Input parameters:

- `limit` (integer)

Output parameters:

- `result` (string)

### `run_summary` (~28 tokens)

Compact summary of one run (accepts trace_id prefix).

Input parameters:

- `trace_id` (string, required)

Output parameters:

- `result` (string)

### `span_tree` (~34 tokens)

Nested span tree of a run — the shape of what the agent did, with durations.

Input parameters:

- `trace_id` (string, required)

Output parameters:

- `result` (string)

### `slowest_spans` (~48 tokens)

Top-k slowest spans. Use for 'why was this run slow?'. Omit trace_id to search all runs.

Input parameters:

- `k` (integer)
- `trace_id`

Output parameters:

- `result` (string)

### `approval_log` (~54 tokens)

Human-in-the-loop audit: every approval/denial/edit, who decided, and the rationale.

Use when asked 'why did the agent get to do X?' or 'what was denied?'.

Input parameters:

- `trace_id`

Output parameters:

- `result` (string)

### `token_usage` (~29 tokens)

Token and cost totals. Omit trace_id to aggregate across all runs.

Input parameters:

- `trace_id`

Output parameters:

- `result` (string)

### `search_spans` (~46 tokens)

Substring search over span names/attributes, e.g. a tool name, file path, or 'denied'.

Input parameters:

- `needle` (string, required)
- `trace_id`

Output parameters:

- `result` (string)

### `failure_report` (~34 tokens)

Show bounded, redacted tool/provider failures and their actionable diagnostics.

Input parameters:

- `limit` (integer)
- `trace_id`

Output parameters:

- `result` (string)

### `tool_stats` (~45 tokens)

Rank tools by errors, denials, latency, and call volume to find unhealthy integrations.

Input parameters:

- `limit` (integer)
- `tool_name`
- `trace_id`

Output parameters:

- `result` (string)

### `security_audit` (~40 tokens)

Audit caller identity, tenant, server provenance, risk, and approval evidence for tool calls.

Input parameters:

- `limit` (integer)
- `trace_id`

Output parameters:

- `result` (string)

### `recent_activity` (~43 tokens)

Poll newly written spans using a cursor; useful while an agent run is still active.

Input parameters:

- `cursor`
- `limit` (integer)
- `trace_id`

Output parameters:

- `result` (string)

### `compare_runs` (~33 tokens)

Compare selected trace-id prefixes for latency, cost, tokens, tools, and failures.

Input parameters:

- `trace_ids` (array, required)

Output parameters:

- `result` (string)

## Diagnostics

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

## Score history

- 2026-10-23: 74
- 2026-10-22: 74
- 2026-10-21: 70
- 2026-10-20: 70
- 2026-10-19: 70
- 2026-10-18: 70
- 2026-10-17: 55
- 2026-10-16: 70
- 2026-10-15: 55
- 2026-10-14: 55
- 2026-10-13: 29

## Common questions

### What is the mcp-trace-inspector server?

mcp-trace-inspector is listed in the public MCP registry as io.github.abhishekash/mcp-trace-inspector. Read local agent-run JSONL traces through MCP for failures, approvals, and run comparisons. This page covers its PyPI package (mcp-trace-inspector).

### Is the mcp-trace-inspector server safe to use?

mcp-trace-inspector scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 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 mcp-trace-inspector server expose?

mcp-trace-inspector exposes 12 tools: list_runs, run_summary, span_tree, slowest_spans, approval_log, and 7 more. Their descriptions and schemas cost roughly 479 tokens of context every time the server is loaded.

### Is the mcp-trace-inspector server still maintained?

mcp-trace-inspector is still listed as active in the MCP registry. We last reached this channel on 23 October 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 mcp-trace-inspector server under?

mcp-trace-inspector 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/mcp-trace-inspector/
- Socket report: https://socket.dev/pypi/package/mcp-trace-inspector
- Changelog RSS feed: https://verifymcp.io/servers/abhishekash-mcp-trace-inspector/mcp-trace-inspector.xml
- Changelog JSON feed: https://verifymcp.io/servers/abhishekash-mcp-trace-inspector/mcp-trace-inspector.json
- HTML version of this page: https://verifymcp.io/servers/abhishekash-mcp-trace-inspector/mcp-trace-inspector