Log Detective MCP
PYPI · LOGDETECTIVE-MCP
MCP server providing log snippet and Python traceback extraction tools.
Available components
Last scanned (17 hours ago)
Scores higher than 82% of PyPI servers
Category Monitoring and Observability
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 31 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 fedora-copr/logdetective-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 15% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 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.
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.6.1 → 0.7.0 functional
- 31 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 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.
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −14
- Malware scan: pass → unverified ▼ security
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 4 Nov 2026 · Analysed pypi/logdetective-mcp@0.7.0
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 | fedora-copr/logdetective-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/fedora-copr/logdetective-mcp/.github/workflows/publish.yml@refs/tags/v0.7.0 |
| Rekor log index | 3638181877 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:c7c8d86f9e4e8347ab4a988497ec603a1767e6285992a786191c9b7b2aaf16ff |
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 31 packages
| Packages resolved | 31 |
|---|---|
| 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 →
extract_log_snippets ~324
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
extract_python_tracebacks ~298
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | integer | – | Number of surrounding lines to include. |
| log_path | string | – | – |
| log_text | string | – | – |
| log_url | string | – | – |
| max_traceback_len | integer | – | – |
| skip_patterns | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
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.
pypi · logdetective-mcp
claude mcp add fedora-copr-logdetective-mcp -- uvx logdetective-mcp
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.