Skip to main content
Glama
nexalware

@nexalware/mcp

Official
by nexalware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @nexalware/mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      Apache 2.0

    • Easy MCP Proxy

      abrookins
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables aggregation, filtering, transformation, and composition of tools from multiple MCP servers through a single proxy with tool views.
      5
      AGPL 3.0

    • Relay

      adarshp14
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.
      173 npm
      MIT

    • McpHub

      John0King
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI tools to uniformly discover, inspect, and call tools, prompts, and resources from multiple upstream MCP servers through a small set of fixed MCP tools, over stdio or HTTP.
      2
      MIT

    • Cybersec Toolkit

      26zl
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP-capable clients to query the tool registry, check install status, get tool recommendations for CTF or bug-bounty work, and run installed security tools through a governed execution path.
      15
      66
      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

    ActivityNo data
    ResponsivenessNo issues

    Resources