# Log Detective MCP (pypi · logdetective-mcp)

MCP server providing log snippet and Python traceback extraction tools.

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

## Components

- pypi · `logdetective-mcp`: 81/100 (this document), [markdown](https://verifymcp.io/servers/fedora-copr-logdetective-mcp/logdetective-mcp.md), [page](https://verifymcp.io/servers/fedora-copr-logdetective-mcp/logdetective-mcp)

## Channel facts

- Registry: `pypi`
- Package: `logdetective-mcp`
- Version: `0.7.0`
- 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-04.

- **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 31 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to fedora-copr/logdetective-mcp).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 2 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 (good).
  - Context-footprint check failed: tool/resource definitions use about 622 tokens (~311/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 76/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 15% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Log Detective MCP server?

Log Detective MCP runs locally as a PyPI package, launched with uvx logdetective-mcp. 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 fedora-copr-logdetective-mcp -- uvx logdetective-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "fedora-copr-logdetective-mcp": {
      "command": "uvx",
      "args": [
        "logdetective-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fedora-copr-logdetective-mcp": {
      "command": "uvx",
      "args": [
        "logdetective-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add fedora-copr-logdetective-mcp -- uvx logdetective-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add fedora-copr-logdetective-mcp --command uvx --arg logdetective-mcp
```

### Hermes

```yaml
mcp_servers:
  fedora-copr-logdetective-mcp:
    command: "uvx"
    args: ["logdetective-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "fedora-copr-logdetective-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "logdetective-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add fedora-copr-logdetective-mcp -t stdio -c uvx -a logdetective-mcp
```

### Other

```json
{
  "mcpServers": {
    "fedora-copr-logdetective-mcp": {
      "command": "uvx",
      "args": [
        "logdetective-mcp"
      ]
    }
  }
}
```

## 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-04 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 66, +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-11-02 (score 65, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.6.1 → 0.7.0

### 2026-10-31 (score 80, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-30 (score 64, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-29 (score 79, +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-28 (score 78, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-27 (score 63, −14)

- [security regression] Malware scan: pass → unverified

## MCP tools (2)

### `extract_log_snippets` (~324 tokens)

Extract representative log snippets using Drain3 clustering.

Analyzes log text by chunking it into logical messages, clustering
similar messages using the Drain algorithm, and returning one
representative snippet per cluster.

Exactly one of log_text, log_path, or log_url must be provided.

Downloaded inputs are limited to 100 MB.
Compressed files (.gz, .bz2, .xz, .zip, .tar, .tar.gz, .tar.bz2,
.tar.xz) are decompressed transparently. Archives must contain
exactly one file. Compression ratios above 100:1 are rejected.

Args:
    log_text: Raw log text to analyze.
    log_path: Path to a log file on disk.
    log_url: HTTP(S) URL to fetch log content from.
    max_clusters: Maximum number of clusters/snippets to extract.
    max_snippet_len: Maximum character length per snippet chunk.
    skip_patterns: Optional list of regex patterns.
        Chunks matching any pattern are excluded before clustering.
    context: Number of lines to include before and after each snippet (0-50).
        These lines are additional to max_snippet_len. Split chunks retain
        their extracted text instead of expanding to the whole source line.

Input parameters:

- `context` (integer): Number of surrounding lines to include.
- `log_path` (string)
- `log_text` (string)
- `log_url` (string)
- `max_clusters` (integer)
- `max_snippet_len` (integer)
- `skip_patterns`

Output parameters:

- `result` (array)

### `extract_python_tracebacks` (~298 tokens)

Extract Python tracebacks using specialized heuristic.

Analyzes log text and extracts unbroken Python tracebacks.
Traces are truncated to `max_traceback_len` characters.

Exactly one of log_text, log_path, or log_url must be provided.

Downloaded inputs are limited to 100 MB.
Compressed files (.gz, .bz2, .xz, .zip, .tar, .tar.gz, .tar.bz2,
.tar.xz) are decompressed transparently. Archives must contain
exactly one file. Compression ratios above 100:1 are rejected.

Args:
    log_text: Raw log text to analyze.
    log_path: Path to a log file on disk.
    log_url: HTTP(S) URL to fetch log content from.
    max_traceback_len: Maximum character length per extracted traceback.
    skip_patterns: Optional list of regex patterns.
        Chunks matching any pattern are excluded.
    context: Number of lines to include before and after each traceback (0-50).
        These lines are additional to max_traceback_len. A truncated
        traceback keeps its shortened text; following context begins after
        the original traceback ends.

Input parameters:

- `context` (integer): Number of surrounding lines to include.
- `log_path` (string)
- `log_text` (string)
- `log_url` (string)
- `max_traceback_len` (integer)
- `skip_patterns`

Output parameters:

- `result` (array)

## Diagnostics

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

## Score history

- 2026-11-04: 81
- 2026-11-03: 66
- 2026-11-02: 65
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 64
- 2026-10-29: 79
- 2026-10-28: 78
- 2026-10-27: 63
- 2026-10-26: 77
- 2026-10-25: 77
- 2026-10-24: 76
- 2026-10-23: 61
- 2026-10-22: 49
- 2026-10-21: 34
- 2026-10-20: 34

## Common questions

### What is the Log Detective MCP server?

Log Detective MCP is listed in the public MCP registry as io.github.fedora-copr/logdetective-mcp. MCP server providing log snippet and Python traceback extraction tools. This page covers its PyPI package (logdetective-mcp).

### Is the Log Detective MCP server safe to use?

Log Detective MCP scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 Log Detective MCP server expose?

Log Detective MCP exposes 2 tools: extract_log_snippets, extract_python_tracebacks. Their descriptions and schemas cost roughly 622 tokens of context every time the server is loaded.

### Is the Log Detective MCP server still maintained?

Log Detective MCP is still listed as active in the MCP registry. We last reached this channel on 4 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 Log Detective MCP server under?

Log Detective MCP declares the Apache-2.0 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/logdetective-mcp/
- Socket report: https://socket.dev/pypi/package/logdetective-mcp
- Repository: https://github.com/fedora-copr/logdetective-mcp
- Changelog RSS feed: https://verifymcp.io/servers/fedora-copr-logdetective-mcp/logdetective-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/fedora-copr-logdetective-mcp/logdetective-mcp.json
- HTML version of this page: https://verifymcp.io/servers/fedora-copr-logdetective-mcp/logdetective-mcp