Skip to main content
Glama
mkcrw

fivem-server-doctor-mcp

by mkcrw

Related Servers

Alternatives to fivem-server-doctor-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Evidence-first MCP server for diagnosing problems with hooks, plugins, skills and configuration, returning ranked probable causes and reviewable fixes without modifying the workspace.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables 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.
      4
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides 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.
      10
      Apache 2.0
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Local repository health diagnosis and fix planning for AI-written JavaScript, TypeScript, Python and mixed projects. Its stdio MCP server exposes scans, finding explanations, repair plans, verification, privacy review and DPDP technical readiness checks.
      214 npm
      32
      GPL 3.0
    • A
      license
      A
      quality
      C
      maintenance
      Lets an MCP client triage a local project for leaked secrets, missing Supabase row-level security, unauthenticated data-changing API routes, insecure browser-exposed environment variables, and other common web-app security mistakes without network access. It returns severity-ordered findings or a plain-English go/no-go summary with what to fix first.
      2
      MIT

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct responsibility: scanning the whole server, inspecting a specific resource, proposing fixes, and applying a single fix. There is no overlap or ambiguity in their purposes.

    Naming Consistency3/5

    Tool names use a two-word underscore pattern, but the verb/noun order is inconsistent: doctor_scan and resource_inspect are object-first, while propose_fixes and apply_fix are verb-first. This mix is still readable but not perfectly predictable.

    Tool Count5/5

    Four tools form a tight, well-scoped workflow for diagnosing and fixing FiveM servers. Each tool adds a necessary stage in the process, and there is no bloat.

    Completeness4/5

    The scan → inspect → propose → apply lifecycle is complete for the core server-doctor functionality. A minor gap is the lack of a revert or validation step after applying a fix, but it can be worked around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues