Skip to main content
Glama
Sign In
@nexalware/mcp

@nexalware/mcp

Official
by nexalware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @nexalware/mcp

No user-submitted related servers found.

    Related Servers

    • Nas.com MCP Server

      Nas-Company
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents and MCP clients to discover and use hosted tools for Nas.com onboarding, business, member, product, and order context, with anonymous discovery and OAuth-gated protected operations.
      MIT

    • Apigee X AI Gateway

      welylau
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover and invoke backend tools over MCP JSON-RPC while enforcing 3-legged OAuth 2.0 identity propagation, role-based access control, and protocol transcoding to REST APIs.
      1
      Apache 2.0

    • SentinelMCP

      ernest-adjetey
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover and invoke versioned external tools through an MCP or REST gateway with authentication, authorization, mutation safety, reliability controls, audit logging, and replay.
      Apache 2.0

    • CLI Anything

      peige-guo
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes approved application capabilities as stable MCP tools, enabling agents to discover and execute read-only operations by default, with optional write or destructive authority for a session.
      MIT
    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.5/5.0

    Scored across 17 tools

    Disambiguation4/5

    Tools are largely distinct by resource (device vs sub-device) and action (telemetry, command, schedule). Minor overlap exists between turn_device_on/off and send_command, and between get_device_commands and get_schedule_context, but descriptions clarify the boundaries.

    Naming Consistency5/5

    All tool names use a consistent snake_case verb_noun pattern (get_, list_, send_, turn_, create_, update_, delete_). The only slight deviation is turn_device_on/off, but it remains readable and consistent with the overall style.

    Tool Count4/5

    17 tools is slightly above the ideal range but justified by the need to cover devices, sub-devices, telemetry, commands, and schedules. Each tool appears to serve a distinct purpose with no redundant operations.

    Completeness4/5

    The surface covers device discovery, command catalog, sending commands, telemetry (latest and history), sub-device operations, and full schedule lifecycle (create/update/delete/list/history/context). Minor gaps exist, such as no device metadata update or sub-device command catalog, but core workflows are complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Resources