troubleshooting-mcp-server (tblakex01/mcp_troubleshooter) is an MCP server listed on the M8ven Trust Index. It scores 43 out of 100, grade D. It declares 7 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
43/100

troubleshooting-mcp-server

A comprehensive MCP server that provides system troubleshooting and diagnostic tools, enabling LLMs to diagnose system issues, monitor resources, check logs, and test connectivity.

→ tblakex01/mcp_troubleshooter· listed on glama

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

tblakex01

Source: Glama

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

Glamanot scored here

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 annotations don’t match behaviour
2 read-only tools perform write/delete/exec — troubleshooting_inspect_environment (line 97: result = subprocess.run(); troubleshooting_execute_safe_command (line 76: result = subprocess.run()
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — troubleshooting_inspect_environment (line 97: result = subprocess.run()
✅
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.
// tools this server exposes7 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.

troubleshooting_inspect_environment

Inspect environment variables and development tool versions.

troubleshooting_read_log_file

Read and tail system log files with optional filtering.

troubleshooting_test_network_connectivity

Test network connectivity to a host and optionally a specific port.

troubleshooting_search_processes

Search for running processes by name pattern with resource usage details.

troubleshooting_monitor_resources

Monitor current system resource usage including CPU, memory, and disk.

troubleshooting_execute_safe_command

Execute whitelisted diagnostic commands safely with timeout protection.

troubleshooting_get_system_info

Get comprehensive system information including OS, hardware, and software versions.

// quality suggestions

Tool annotations match behaviour

2 read-only tools perform write/delete/exec — troubleshooting_inspect_environment (line 97: result = subprocess.run(); troubleshooting_execute_safe_command (line 76: result = subprocess.run()

Either remove the readOnlyHint:true annotation, or remove the write/delete call from the tool handler.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — troubleshooting_inspect_environment (line 97: result = subprocess.run()

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

Tests exist

No test files found

Add tests that exercise each declared tool.

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 3 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/tblakex01/mcp_troubleshooter?variant=verified)](https://m8ven.ai/mcp/tblakex01/mcp_troubleshooter)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 8f95631f535a01a2dbe08196fd5a6977fbc42100
code hash: 5b13dad101d5d40167f26d060d8cecf273331891392dc0649da2962bf5fc0cd7
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