Backend Investigator MCP Server

by mrzedov Your server? Claim it

local only

Backend Investigator runs on your own machine — the client starts it, so there is no endpoint to ping. 497 installs a week from npm.

Read-only diagnostics: Loki, Prometheus, PostgreSQL, Redis, BullMQ, Docker and GitHub.

Installs per day peak 273 · avg 26

a month agotoday

497

Installs / week

npm · @mr.zedov/backend-investigator

—

Stars

on GitHub

—

Last commit

5 releases in 90 days

—

License

language unknown

Nothing serious here today

Today is the operative word: we check Backend Investigator every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add backend-investigator -- npx -y @mr.zedov/backend-investigator

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "backend-investigator": {
      "args": [
        "-y",
        "@mr.zedov/backend-investigator"
      ],
      "command": "npx"
    }
  }
}

~/.codex/config.toml

[mcp_servers.backend-investigator]
command = "npx"
args = ["-y", "@mr.zedov/backend-investigator"]

.cursor/mcp.json

{
  "mcpServers": {
    "backend-investigator": {
      "args": [
        "-y",
        "@mr.zedov/backend-investigator"
      ],
      "command": "npx"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "backend-investigator": {
      "args": [
        "-y",
        "@mr.zedov/backend-investigator"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: BACKEND_INVESTIGATOR_TELEMETRY (Set false to force off optional usage statistics. No events before explicit consent. true does not grant consent.), BACKEND_INVESTIGATOR_WORKSPACE (Optional absolute Linux/WSL application root initialized with setup. Restricts tools and history to its bound project. Omit only for intentional shared mode.). The author declared them in the registry entry; get the values from the project itself.

Alternatives to Backend Investigator

same job, measured the same way

Navigator

by mentu

Read-only repo navigation and progressive disclosure; BM25 locator with registered evidence.

48 installs/wk local only

MCP Netassist

by edge-echo

Windows network and proxy diagnostics: GitHub reachability, proxy ports, DNS/TCP, and fixes.

51 installs/wk local only

LDAP Assistant MCP

by droideck

MCP server for 389 Directory Server health diagnostics, log analysis, and SOS-report investigation

70 installs/wk local only

gha-doctor

by linnea-bakshi

Diagnose GitHub Actions CI: lint, flaky tests, wasted minutes, health score. Read-only MCP tools.

local only

BackendGen

by sitouhemi

Validate compact backend specs and generate tested NestJS, Prisma, and PostgreSQL repositories.

39 installs/wk local only

Project Brain

by gentleelephant

Read-only source search and retrieval across configured GitHub repositories

local only

GitHub (read-only)

by abdulmuhaiminkhan

Read-only GitHub repos, issues, PRs and commits, with tool descriptions tuned on a benchmark.

121 installs/wk local only

Tiger Skills

by timescale

Provider agnostic skills implementation, with skills sourced from local paths or GitHub repositories

46 installs/wk local only

Backend Investigator — questions

Answers built from our own checks of this server.

Why is there no uptime for Backend Investigator?

Backend Investigator runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @mr.zedov/backend-investigator was installed 497 times last week.

How do I connect Backend Investigator?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @mr.zedov/backend-investigator straight from npm; nothing to host, nothing to sign up for.

How many people use Backend Investigator?

The npm package @mr.zedov/backend-investigator was installed 497 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.