boot-doctor-mcp
Related Servers
Alternatives to boot-doctor-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityDmaintenanceExpert system hardware probe and performance diagnostic engine for AI, Gaming, and High-Performance workflows. Provides deep system insights such as real-time monitoring, thermal diagnostics, and LLM optimization.1141 npm7Apache 2.0- AlicenseNot gradedqualityCmaintenanceEnables read-only inspection and diagnosis of Windows, macOS, and Linux machines through eight diagnostic tools covering system profiles, baselines, disk health, startup audits, driver context, and upgrade planning, with voice summaries and a web simulator. It enforces an R0-R3 risk model in code so only safe R0 evidence collection is automatic while riskier actions remain manual guidance.MIT
- AlicenseAqualityAmaintenanceEnables AI agents to diagnose broken XAMPP/WAMP localhost stacks by inspecting real machine state — running processes, listening ports, HTTP probes, and Apache/MySQL error logs — to pinpoint port conflicts, startup crashes, unclean-shutdown damage, and zombie processes with plain-English explanations. All diagnostics are read-only, so agents can safely answer questions like why Apache won't start or why localhost refuses to connect instead of guessing.4MIT
- FlicenseAqualityDmaintenanceEnables LLM-driven agents to autonomously detect, diagnose, repair, verify, and prevent software and hardware failures on local and remote systems. Includes built-in safety checks and automatic rollbacks.15-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to diagnose, troubleshoot, and manage PC settings on Windows, macOS, and Linux through natural language commands.GPL 3.0
- AlicenseNot gradedqualityCmaintenanceChecks PC component compatibility and estimates power supply requirements from user-supplied specifications, returning structured conflicts, fixes, and recommended PSU capacity.MIT
TDQS
Scored across 2 tools
The two tools serve completely different purposes: diagnose_symptoms walks through a troubleshooting decision tree, while lookup_beep_code is a reference lookup. There's zero overlap or ambiguity about which to call in any scenario.
Both tools follow the identical imperative verb_noun snake_case convention (diagnose_symptoms, lookup_beep_code). Perfect consistency, even if the sample size is small.
Two tools is on the thin side for a general-purpose troubleshooting server, but the scope here is deliberately narrow (diagnosis guidance + beep-code reference). It works, but feels minimal.
The core workflows (symptom-based guidance and beep-code lookup) are covered, but natural additions like a debug-LED/literal code reference, or a POST-code table, would round out the domain. Notable but not critical gaps.