Backend Investigator
Rank #52,553io.github.mrZedov/backend-investigator
Read-only diagnostics: Loki, Prometheus, PostgreSQL, Redis, BullMQ, Docker and GitHub.
What you can do with Backend Investigator
Backend Investigator is a Model Context Protocol (MCP) server. It ranks #52,553 of 151,203 active servers on MCP Toplist. Backend Investigator is listed on Official MCP, with 6 tracked versions. It was first listed on Oct 5, 2026 and most recently updated on Oct 13, 2026.
Not verifiedMCP Toplist has not yet written a checked profile for this server, so the paragraph above is assembled from registry data only. Its registry listings below are the authority on what it does.
What Backend Investigator can and cannot do
Not verifiedMCP Toplist has not catalogued this server's tools or limitations. Check its registry listings below.
What you need before using Backend Investigator
The registry listing declares no required environment variables or authentication. This is declared metadata, not a verified install — the repository README is the authority.
Declared by the Official MCP Registry, last synced Oct 23, 2026. Not independently verified by MCP Toplist.
- BACKEND_INVESTIGATOR_TELEMETRY · optional
- BACKEND_INVESTIGATOR_WORKSPACE · optional
Connect Backend Investigator and confirm it works
claude mcp add backend-investigator -e "BACKEND_INVESTIGATOR_TELEMETRY=<your BACKEND_INVESTIGATOR_TELEMETRY>" -e "BACKEND_INVESTIGATOR_WORKSPACE=<your BACKEND_INVESTIGATOR_WORKSPACE>" -- npx -y @mr.zedov/backend-investigatorReplace each placeholder with your own value before saving.
[mcp_servers.backend-investigator]
command = "npx"
args = ["-y", "@mr.zedov/backend-investigator"]
[mcp_servers.backend-investigator.env]
BACKEND_INVESTIGATOR_TELEMETRY = "<your BACKEND_INVESTIGATOR_TELEMETRY>"
BACKEND_INVESTIGATOR_WORKSPACE = "<your BACKEND_INVESTIGATOR_WORKSPACE>"Add to ~/.codex/config.toml. Replace each placeholder with your own value before saving.
{
"mcpServers": {
"backend-investigator": {
"command": "npx",
"args": [
"-y",
"@mr.zedov/backend-investigator"
],
"env": {
"BACKEND_INVESTIGATOR_TELEMETRY": "<your BACKEND_INVESTIGATOR_TELEMETRY>",
"BACKEND_INVESTIGATOR_WORKSPACE": "<your BACKEND_INVESTIGATOR_WORKSPACE>"
}
}
}
}Add to claude_desktop_config.json (Settings → Developer → Edit Config). Replace each placeholder with your own value before saving.
{
"mcpServers": {
"backend-investigator": {
"command": "npx",
"args": [
"-y",
"@mr.zedov/backend-investigator"
],
"env": {
"BACKEND_INVESTIGATOR_TELEMETRY": "<your BACKEND_INVESTIGATOR_TELEMETRY>",
"BACKEND_INVESTIGATOR_WORKSPACE": "<your BACKEND_INVESTIGATOR_WORKSPACE>"
}
}
}
}Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). Replace each placeholder with your own value before saving.
{
"servers": {
"backend-investigator": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mr.zedov/backend-investigator"
],
"env": {
"BACKEND_INVESTIGATOR_TELEMETRY": "<your BACKEND_INVESTIGATOR_TELEMETRY>",
"BACKEND_INVESTIGATOR_WORKSPACE": "<your BACKEND_INVESTIGATOR_WORKSPACE>"
}
}
}
}Save as .vscode/mcp.json in your workspace. Replace each placeholder with your own value before saving.
{
"mcpServers": {
"backend-investigator": {
"command": "npx",
"args": [
"-y",
"@mr.zedov/backend-investigator"
],
"env": {
"BACKEND_INVESTIGATOR_TELEMETRY": "<your BACKEND_INVESTIGATOR_TELEMETRY>",
"BACKEND_INVESTIGATOR_WORKSPACE": "<your BACKEND_INVESTIGATOR_WORKSPACE>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json. Replace each placeholder with your own value before saving.
{
"mcpServers": {
"backend-investigator": {
"command": "npx",
"args": [
"-y",
"@mr.zedov/backend-investigator"
],
"env": {
"BACKEND_INVESTIGATOR_TELEMETRY": "<your BACKEND_INVESTIGATOR_TELEMETRY>",
"BACKEND_INVESTIGATOR_WORKSPACE": "<your BACKEND_INVESTIGATOR_WORKSPACE>"
}
}
}
}Replace each placeholder with your own value before saving.
After adding the config, ask your client to list this server's tools. A tool list confirms the connection; an empty list or an error means the server did not start or needs credentials.
What changed, and when this was checked
- First listed
- Oct 5, 2026
- Latest version published
- Oct 13, 2026
- Version history
- 6 versions tracked (below)
- Requirements evidence
- Declared by the Official MCP Registry, last synced Oct 23, 2026. Not independently verified by MCP Toplist.
- Profile checked
- Not yet — purpose, capabilities and requirements above come from registry data only
- Ranking data as of
- Oct 13, 2026
- Official MCP ↗listed since Oct 6, 2026 · still listed
Do you maintain Backend Investigator? to correct or enrich this profile.
Available versions (6)
| Version | Published |
|---|---|
| 1.7.1 | Oct 13, 2026 |
| 1.7.0 | Oct 8, 2026 |
| 1.6.2 | Oct 7, 2026 |
| 1.5.0 | Oct 6, 2026 |
| 1.3.0 | Oct 5, 2026 |
| 1.2.0 | Oct 5, 2026 |
Ranks ahead of 98,650 of 151,203 servers on MCP Toplist.
Show your rank
Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.
[](https://mcptoplist.com/server/io.github.mrZedov%2Fbackend-investigator)<a href="https://mcptoplist.com/server/io.github.mrZedov%2Fbackend-investigator"><img src="https://mcptoplist.com/badge/io.github.mrZedov%2Fbackend-investigator.svg" alt="MCP Toplist: Top 50% of 151,203" /></a>Variants: append ?metric=score or ?metric=stars to the image URL.
Frequently asked questions
- Is Backend Investigator listed on the Official MCP Registry?
- Yes — Backend Investigator is listed on the Official MCP Registry.
- How many versions does Backend Investigator have?
- MCP Toplist tracks 6 versions of Backend Investigator, most recently published on Oct 13, 2026.
Do you run this server?
Community projects list the MCP servers behind real agents and apps. Publish yours and this page will link to it.