Skip to main content
Glama
ZenixSolutions

lumics-mcp

Related Servers

Alternatives to lumics-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that exposes live network monitoring data as Resources and diagnostic capabilities as Tools, letting AI assistants query network health conversationally.
      6
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for Domotz network monitoring and management. Enables AI assistants to query network devices, alerts, and topology via the Domotz API.
      2
      23 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for the Pingera monitoring service, providing seamless integration between AI models and monitoring data.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for network operations that lets AI assistants interact with Cisco/Juniper network devices through safe, well-defined tools like compliance audits and configuration backups.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      This project provides a Model Context Protocol (MCP) server that allows language models and other MCP clients to interact with a SuzieQ network observability instance via its REST API.
      2
      4
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides AI agents with seamless access to the NetSapiens VoIP platform for user management, call analytics, and system administration.
      23
      4
      -

    TDQS

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are completely distinct: one returns platform metadata about component definitions, the other returns the authenticated user and company. There is zero overlap in purpose or output, so an agent could not confuse them.

    Naming Consistency5/5

    Both tools share the exact 'lumics_get_' verb_noun pattern, making the naming predictable and consistent. The names clearly convey that these are read-only retrieval operations.

    Tool Count3/5

    With only two tools, the set feels thin, but the descriptions explicitly indicate that these are the bootstrap tools available when no company ID is configured. For that restricted state, the count is reasonable, though the overall server scope is clearly larger.

    Completeness2/5

    The tool surface is severely limited: it only provides identity and platform metadata. There are no operations for managing devices, collectors, components, or other tenant data, which seems to be the server's broader purpose. This is likely a deliberate degraded mode, but as a standalone set it leaves agents unable to perform meaningful domain work.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive