Log Analyzer MCP Server
log-analyzer-mcp
PyPI
v0.1.8
Published by nold-ai — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server and tools for analyzing test and runtime logs.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
low Shell/command execution in packaging/dev tooling (tests/log_analyzer_mcp/test_log_analyzer_mcp_server.py)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/log_analyzer_mcp/test_log_analyzer_mcp_server.py:316`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ss server_process = subprocess.Popen( [sys.executable, server_path, "--transport", "stdio"], stdin=s
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tests/log_analyzer_mcp/test_log_analyzer_mcp_server.py
Tools 12
Each tool and what it can reach — statically extracted from the published source.
analyze_testsno sensitive capabilitycreate_coverage_reportno sensitive capabilityget_server_env_detailsno sensitive capabilitypingno sensitive capabilityrun_tests_no_verbosityno sensitive capabilityrun_tests_verboseno sensitive capabilityrun_tests_very_verboseno sensitive capabilityrun_unit_testno sensitive capabilitysearch_log_all_recordsno sensitive capabilitysearch_log_first_n_recordsno sensitive capability
Show 2 more tools ↓
search_log_last_n_recordsno sensitive capabilitysearch_log_time_basedno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (12 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.8 latest |
A 99/100 | 1 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan log-analyzer-mcp --online --registry pypiMore in Files & Storage
Safe bulk Meta ads: launch 150+ campaigns from Drive folders with spend guardrails and validation.
CLI tool to add MCP servers to various AI coding clients
MCP compatibility adapter for Agent Tool Protocol
MCP server for multi-tenant DuckDB management with R2/S3 storage
A stdio-to-HTTP MCP proxy that transparently intercepts file parameters, reading local files and base64-encoding them before forwarding to the remote server.
Free buyer-side outcome verification and provider comparison for supplied agent receipts.