Debug MCP server

by standardbeagle·io.github.standardbeagle/mcp-debug·v1.1.6

Debug and develop MCP servers with hot-swapping, session recording, and playback testing

C62/100grade C

What users say

No reviews yet

Safety scan

C62/100

Adoption

New

0 stars

Reviews

Nobody has reviewed Debug yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

No tool declarations could be read from the package source. They show once the server is installed.

scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it

2 medium

Code scan3 source files scanned; 4 source files scanned15/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 267 days ago4/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

mediumnpm install lifecycle script presentinstall.script

package.json: …ebug": "bin.js" }, "scripts": { "postinstall": "node install.js" }, "repository": …

Overall 62/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

claude mcp add mcp-debug -- uvx mcp-debug

Is Debug MCP server safe?: With care: it is graded C, so read the findings first (62/100). Read the Debug safety report
How do I install Debug?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Debug need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Debug maintained?: The last commit was 279 days ago (2026-01-07). The latest release is v1.1.6.