Skip to main content
Glama
lchampz

mcp-heimdall

by lchampz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-heimdall

No user-submitted related servers found.

    Related Servers

    • MCP Troubleshooter

      devlimelabs
      A
      license
      C
      quality
      D
      maintenance
      A specialized diagnostic framework that enables AI models to self-diagnose and fix MCP-related issues by analyzing logs, validating configurations, testing connections, and implementing solutions.
      9
      MIT

    • MCP Store

      Meir83
      A
      license
      Not graded
      quality
      C
      maintenance
      A comprehensive MCP server for IT, DBA, and developer tasks, enabling error resolution, task automation, performance monitoring, automated documentation, and configuration management.
      1 npm
      ISC

    • minecraft-diagnostic-mcp

      Monasik
      A
      license
      Not graded
      quality
      D
      maintenance
      An external MCP server for diagnosing Minecraft servers via backup analysis, local runtime, or Docker runtime, offering tools for plugin inspection, log analysis, configuration linting, and performance diagnostics.
      1
      MIT

    • Env Validator

      pouyasadri
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP (Model Context Protocol) server that inspects your local development environment and reports missing dependencies, version mismatches, and misconfigured environment variables to any MCP-compatible AI assistant. Works with Claude Desktop, Cursor, Gemini CLI, and any other client that supports stdio-transport MCP servers.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool addresses a distinct aspect of system health: auditing dependencies, environment, connectivity, Docker, runtimes, processes, ports, PATH, resource usage, vulnerabilities, and cleanup. No two tools overlap in purpose; even related tools like 'list_ports' and 'kill_port_process' are clearly separated.

    Naming Consistency4/5

    Most tools follow a verb_noun or descriptive pattern (e.g., audit_dependencies, check_connectivity, kill_port_process). However, some use noun_noun (path_inspector, process_explorer, resource_watcher) which introduces minor inconsistency but remains readable and predictable.

    Tool Count5/5

    With 14 tools covering diagnostics, inspection, and maintenance actions, the count is well-scoped for a system health server. Each tool earns its place, and the number is within the ideal 3-15 range.

    Completeness5/5

    The server covers a comprehensive set of system checks: OS, processes, ports, Docker, runtimes, dependencies, environment, connectivity, resource usage, vulnerabilities, and disk cleanup. The inclusion of 'suggest_corrections' that runs all diagnostics and gives prioritized fixes rounds out the surface with no obvious gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources