Skip to main content
Glama
geoffbelknap

LimaCharlie MCP

by geoffbelknap

Related Servers

Alternatives to LimaCharlie MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      A read-only MCP server for Microsoft Intune and Entra ID that enables list, get, search, and reporting operations for tenant visibility, audits, troubleshooting, and health reporting without write actions. It includes authentication helpers, report exports, and metadata discovery tools.
      36
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that provides tools to list and read devices, MDM servers, blueprints, configurations, apps, packages, users, and other resources from Apple Business Manager and Apple School Manager.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A secure, local-first MCP server for read-only inspection and troubleshooting of development environments, exposing narrow, typed, auditable capabilities for repository inspection, log summarization, Docker review, and security scanning without granting unrestricted machine access.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server to inspect allowlisted Docker containers, systemd services, JSONL logs, and HTTP health endpoints without arbitrary shell access.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server for observing registered local and SSH hosts, providing system, service, container, Git, and GPU status/log inspection through a closed-world registry without arbitrary shell access.
      -

    TDQS

    C2.4/5.0

    Scored across 297 tools

    Disambiguation2/5

    The tool set contains many near-identical resource families, such as list/get/preview_set/preview_delete/preview_set_enabled wrappers for secrets, lookups, cloud adapters, external adapters, playbooks, SOPs, org notes, AI agents, AI skills, and generic Hive records. Memory tools like lc_get_ai_memory, lc_get_ai_memory_record, lc_list_ai_memories, and lc_list_ai_memory_records further blur boundaries, making misselection likely.

    Naming Consistency4/5

    Most tools follow a consistent lc_verb_noun pattern, especially list/get/preview_set/preview_delete, which is helpful at scale. However, there are minor deviations such as lc_auth_whoami, lc_tool_catalog, lc_fetch_config, and the mixed use of preview_set versus preview_create/preview_update for similar operations.

    Tool Count1/5

    297 tools is an extreme count for any MCP server, far beyond the well-scoped range. Even with LimaCharlie's broad platform surface, this volume overwhelms agents and makes tool selection and reasoning impractical.

    Completeness4/5

    The tool surface is exceptionally broad, covering org management, sensors, detections, cases, D&R rules, Hive records, vulnerability data, AI sessions, and many extension-based workflows. Minor lifecycle gaps exist, such as no single-output get/update, no case deletion, and no case-note update/delete, but most workflows can proceed without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues