debuggai (kyliladevious262/debuggai) is an MCP server listed on the M8ven Trust Index. It scores 73 out of 100, grade C. It declares 17 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
73/100

debuggai

Detect AI code bugs, security flaws, and API mismatches before production with a universal verification layer for generated software

→ kyliladevious262/debuggai· listed on github_repo_search

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

kyliladevious262

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Tool descriptions don’t match what handlers do
2 tools describe read intent but their handlers mutate — get_report (line 18: spawn("debuggai", [...args, "--format", "json"], {); configure (line 18: spawn("debuggai", [...args, "--format", "json"], {)
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: ANTHROPIC_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes14 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

scan_code

Scan code for AI-generated bugs, security issues, and performance problems

verify_intent

Verify code matches a natural language intent. Returns Prompt Fidelity Score.

get_report

Get a full DebuggAI report in JSON format for programmatic analysis

configure

Show or initialize DebuggAI configuration for the current project

init_project

Initialize DebuggAI for a project. Auto-detects languages and creates config.

fix_issues

Generate fixes for detected issues. Optionally auto-apply high-confidence fixes.

show_history

Show scan history and quality trends for the current project.

dismiss_rule

Dismiss an issue rule. After 3 dismissals of the same rule, it auto-suppresses.

deep_analysis

Run deep architectural analysis — finds system-level bugs that pattern matching misses.

discover_personas

Discover who uses this software. Identifies ICPs (Ideal Customer Personas) from the codebase.

persona_test

Test software from the customer's perspective. Finds UX issues specific to each persona.

start_persona_session

Start a live persona testing session. Opens a real browser and navigates to the URL.

execute_persona_action

Execute the persona's next action and capture the new page state.

end_persona_session

End the live persona testing session and get the experience report.

// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretANTHROPIC_API_KEY
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

17/17 tools missing one or more hints — scan_code (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); verify_intent (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_report (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +14 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Descriptions match behaviour

2 tools describe read intent but their handlers mutate — get_report (line 18: spawn("debuggai", [...args, "--format", "json"], {); configure (line 18: spawn("debuggai", [...args, "--format", "json"], {)

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool test coverage

Only 2/17 tools referenced in tests (12%)

Write tests that reference each tool by name so every tool has at least one test.

Tool description accuracy

get_report: description implies read-only but handler writes/deletes/executes; configure: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/kyliladevious262/debuggai?variant=verified)](https://m8ven.ai/mcp/kyliladevious262/debuggai)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 150bfb91d2d36121eded56ff4e609e65582686b8
code hash: 75528e20f8a93cca39a10904c2a7cadbcdd84e520a1b2d446e720a5b31ded264
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client