# @mr.zedov/backend-investigator

Read-only backend investigations with Loki, Prometheus, PostgreSQL, Redis, BullMQ, Docker and GitHub.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.7.1
- **Author:** io.github.mrZedov
- **License:** SEE LICENSE IN Backend Investigator Free Use License.txt
- **npm:** @mr.zedov/backend-investigator
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-14T04:47:21.377Z
- **Version scanned:** 1.7.1
- **CVEs:** none found by OSV at scan time

## Tools

14 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `list_projects` — List configured projects with pagination. Use this first to select a projectId; no connection credentials are returned.
- `get_project_capabilities` — Discover enabled sources and available read-only checks for a project before choosing follow-up tools. Source IDs are included, connection configuration is not.
- `investigate_backend` — Primary high-level tool: conservatively select a strategy from an unambiguous question or explicit strategy. Unknown/mixed questions preserve full health checks
- `investigate_operation` — 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.
- `investigate_deployment_regression` — Compare evidence before/after an observed successful deployment or explicitly labelled release marker. Uses compatible archived snapshots and historical logs; m
- `list_investigations` — List immutable saved investigation summaries with pagination and optional projectId filter. Historical projects need not still exist; credentials and raw logs a
- `get_investigation` — Retrieve an immutable investigation snapshot by investigationId, with paginated summarized evidence, findings, accepted hypotheses and source availability. Evid
- `get_latest_deployment` — Read latest/previous GitHub deployments using success-status timestamps, or explicitly enabled local demo-only simulated switches. Releases are publication mark
- `inspect_service` — Follow up on a Docker service/container by its exact serviceId and sourceId. Reads runtime inventory, health, optional stats and recent restarts; never restarts
- `inspect_database` — Read PostgreSQL health, current sessions and blocking locks. For a performance review explicitly request performanceChecks: query_statistics (pg_stat_statements
- `inspect_metrics` — Read fixed, scoped Prometheus range queries: availability (scrape targets), http (request rate, 5xx percent, classic histogram p95/p99) and resources (process C
- `inspect_redis` — Read Redis health and sanitized SLOWLOG samples for a configured source. Never scans all keys, reads values or executes write commands.
- `inspect_queue` — Read BullMQ counts, worker visibility and sanitized bounded job samples for a configured queue. No job retry, removal or state changes are exposed.
- `search_logs` — 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; configure

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"backend-investigator\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@mr.zedov/backend-investigator\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40mr.zedov%2Fbackend-investigator
- Install plan: https://forgeregistry.com/api/v1/packages/%40mr.zedov%2Fbackend-investigator/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40mr.zedov%2Fbackend-investigator
- HTML page: https://forgeregistry.com/registry/%40mr.zedov%2Fbackend-investigator
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.