Backend Investigator
NPM · @MR.ZEDOV/BACKEND-INVESTIGATOR
Read-only diagnostics: Loki, Prometheus, PostgreSQL, Redis, BullMQ, Docker and GitHub.
Available components
Last scanned (7 hours ago)
Scores higher than 36% of npm 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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 43 of 151 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 3 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1287 tokens (~91/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 14 Oct 26 +26
- 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). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ 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 functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 13 Oct 26 0
- Package version: 1.7.0 → 1.7.1 functional
- 11 Oct 26 0
- Package version: 1.5.0 → 1.7.0 functional
- 7 Oct 26 31
First indexed and scored.
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 17 Oct 2026 · Analysed npm/@mr.zedov/backend-investigator@1.7.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 151 packages
| Packages resolved | 151 |
|---|---|
| Stale | 43 |
| 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 →
get_investigation ~75
Retrieve an immutable investigation snapshot by investigationId, with paginated summarized evidence, findings, accepted hypotheses and source availability. Evidence references may point to another page. No live source or deleted project credentials are required.
| Name | Type | Req | Description |
|---|---|---|---|
| evidenceLimit | integer | – | – |
| evidenceOffset | integer | – | – |
| investigationId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| status | string | yes | – |
No examples provided.
get_latest_deployment ~83
Read latest/previous GitHub deployments using success-status timestamps, or explicitly enabled local demo-only simulated switches. Releases are publication markers, never claimed rollout times. Build historical before/after windows without changing infrastructure.
| Name | Type | Req | Description |
|---|---|---|---|
| afterMinutes | integer | – | – |
| beforeMinutes | integer | – | – |
| projectId | string | yes | – |
| sourceId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| status | string | yes | – |
No examples provided.
get_project_capabilities ~45
Discover enabled sources and available read-only checks for a project before choosing follow-up tools. Source IDs are included, connection configuration is not.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| status | string | yes | – |
No examples provided.
inspect_database ~132
Read PostgreSQL health, current sessions and blocking locks. For a performance review explicitly request performanceChecks: query_statistics (pg_stat_statements), tables, indexes, vacuum, io. Optional checks use bounded fixed read-only queries and report availability/reasons individually. performanceLimit defaults to 5 rows per sample (maximum 20); cumulative statistics are not a recent time window. No arbitrary SQL, EXPLAIN ANALYZE, query cancellation or maintenance is exposed.
| Name | Type | Req | Description |
|---|---|---|---|
| performanceChecks | array | – | – |
| performanceLimit | integer | – | – |
| projectId | string | yes | – |
| sourceId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| status | string | yes | – |
No examples provided.
inspect_metrics ~164
Read fixed, scoped Prometheus range queries: availability (scrape targets), http (request rate, 5xx percent, classic histogram p95/p99) and resources (process CPU cores and resident bytes). No arbitrary PromQL or writes. Windows are at most 24 hours with at most 21 evaluation points. Missing data/non-finite values are explicit. Optional equal-length earlier comparison windows report sampled-mean deltas, not causal proof or whole-window percentiles.
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | – |
| compareFrom | string | – | – |
| compareTo | string | – | – |
| from | string | – | – |
| projectId | string | yes | – |
| sourceId | string | yes | – |
| stepSeconds | integer | – | – |
| to | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| status | string | yes | – |
No examples provided.
inspect_queue ~59
Read BullMQ counts, worker visibility and sanitized bounded job samples for a configured queue. No job retry, removal or state changes are exposed.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
| queue | string | yes | – |
| sourceId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| status | string | yes | – |
No examples provided.
inspect_redis ~51
Read Redis health and sanitized SLOWLOG samples for a configured source. Never scans all keys, reads values or executes write commands.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
| sourceId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| status | string | yes | – |
No examples provided.
inspect_service ~68
Follow up on a Docker service/container by its exact serviceId and sourceId. Reads runtime inventory, health, optional stats and recent restarts; never restarts or modifies containers.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
| serviceId | string | yes | – |
| sourceId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| status | string | yes | – |
No examples provided.
investigate_backend ~128
Primary high-level tool: conservatively select a strategy from an unambiguous question or explicit strategy. Unknown/mixed questions preserve full health checks. Conditional checks require observed dependency hints; irrelevant sources are skipped. Returns execution decisions, facts and optional reasoning; configured history appends a local immutable archive.
| Name | Type | Req | Description |
|---|---|---|---|
| afterMinutes | integer | – | – |
| beforeMinutes | integer | – | – |
| deploymentId | string | – | – |
| operation | object | – | – |
| projectId | string | yes | – |
| question | string | – | – |
| sourceId | string | – | – |
| strategy | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| status | string | yes | – |
No examples provided.
investigate_deployment_regression ~127
Compare evidence before/after an observed successful deployment or explicitly labelled release marker. Uses compatible archived snapshots and historical logs; missing baselines are not zero. Separates changes, unchanged metrics, time correlation and optional hypotheses. Current follow-up checks are not historical evidence. Appends an immutable local archive when configured.
| Name | Type | Req | Description |
|---|---|---|---|
| afterMinutes | integer | – | – |
| beforeMinutes | integer | – | – |
| deploymentId | string | – | – |
| logLimit | integer | – | – |
| projectId | string | yes | – |
| question | string | – | – |
| sourceId | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| status | string | yes | – |
No examples provided.
investigate_operation ~142
Investigate a specific endpoint or operation in one service/log source and explicit time window. Match route or query, then correlate sampled request/trace IDs. Live infrastructure anomalies are only temporally related, not proof of causation. When history is configured, appends a local archive without changing connected infrastructure.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | – |
| logLimit | integer | – | – |
| method | string | – | – |
| projectId | string | yes | – |
| query | string | – | – |
| question | string | – | – |
| route | string | – | – |
| serviceId | string | yes | – |
| sourceId | string | yes | – |
| to | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| status | string | yes | – |
No examples provided.
list_investigations ~61
List immutable saved investigation summaries with pagination and optional projectId filter. Historical projects need not still exist; credentials and raw logs are not loaded.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| projectId | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| status | string | yes | – |
No examples provided.
list_projects ~43
List configured projects with pagination. Use this first to select a projectId; no connection credentials are returned.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| status | string | yes | – |
No examples provided.
search_logs ~109
Search bounded Docker or scoped Loki logs by optional serviceId and literal substring query. For Loki, serviceId is the source ID, not a container ID; configured labels cannot be overridden. Use a narrower explicit time window/query if sampled or oversized.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | – |
| limit | integer | – | – |
| projectId | string | yes | – |
| query | string | – | – |
| serviceId | string | – | – |
| sourceId | string | yes | – |
| to | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | object | – | – |
| status | string | yes | – |
No examples provided.
How do I install the Backend Investigator MCP server?
Backend Investigator runs locally as an npm package, launched with npx -y @mr.zedov/backend-investigator. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mr.zedov/backend-investigator
claude mcp add mrzedov-backend-investigator -- npx -y @mr.zedov/backend-investigator
What is the Backend Investigator MCP server?
Backend Investigator is an MCP server listed in the public MCP registry as io.github.mrZedov/backend-investigator. Read-only diagnostics: Loki, Prometheus, PostgreSQL, Redis, BullMQ, Docker and GitHub. This page covers its npm package (@mr.zedov/backend-investigator).
Is the Backend Investigator MCP server safe to use?
Backend Investigator scores 57 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. 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 Backend Investigator MCP server expose?
Backend Investigator exposes 14 tools: list_projects, get_project_capabilities, investigate_backend, investigate_operation, investigate_deployment_regression, and 9 more. Their descriptions and schemas cost roughly 1,287 tokens of context every time the server is loaded.
Is the Backend Investigator MCP server still maintained?
Backend Investigator is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.