Localhost Doctor
Related Servers
Alternatives to Localhost Doctor
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceProvides AI coding agents with structured, evidence-based diagnostics about the local development environment, detecting tech stack, runtime mismatches, dependency state, services, ports, and Git status without exposing secrets or using network calls.10Apache 2.0
- FlicenseBqualityDmaintenanceProvides Windows system diagnostic capabilities to AI agents, allowing them to access event logs, crash information, system uptime, and perform stability analysis.113-
- AlicenseNot gradedqualityDmaintenanceEnables LLM clients to inspect local dev environments—Docker container health, pnpm workspace integrity, and stuck process detection—without manual terminal copy-pasting.MIT
- FlicenseAqualityBmaintenanceProvides AI coding agents with real-time visibility into local development runtime state, enabling them to tail application logs, inspect ports, monitor process metrics, and diagnose network errors.1-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to debug local networks in plain language by pinging, sweeping subnets, tracing routes, resolving DNS, scanning ports, inspecting ARP tables and active connections, and checking URL reachability.MIT
- FlicenseNot gradedqualityCmaintenanceEnables an AI assistant to diagnose a local WordPress install by listing plugins, checking PHP/WP environment, tailing debug logs, running guarded read-only SQL queries, and inspecting Gravity Forms error and add-on logs.-
TDQS
Scored across 4 tools
Each tool has a distinct primary angle (full diagnosis, single-port lookup, log reading, symptom explanation), so an agent can usually pick correctly. However, diagnose_stack already reports port ownership and verdicts, overlapping with check_port, and explain_symptom overlaps with read_error_logs' error-explanation role, creating mild risk of redundancy-driven misselection.
All four tools follow a clean verb_noun snake_case pattern: diagnose_stack, check_port, read_error_logs, explain_symptom. No deviations or mixed conventions.
Four tools is well-scoped for a local stack diagnostic helper, with each tool covering a recognizable facet of the problem space without bloat.
The surface covers diagnosis, port inspection, log reading, and symptom explanation, which matches the 'doctor' diagnostic purpose. Minor gap: no remediation tool (e.g., restart service or free a port) for when a conflict or degraded verdict is found, leaving agents to advise manually.