Skip to main content
Glama
NexaLayer

nexalayer-mcp

Official
by NexaLayer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to nexalayer-mcp

No user-submitted related servers found.

    Related Servers

    • anthropic_skill

      williamchek
      F
      license
      Not graded
      quality
      D
      maintenance
      A robust, lightweight Model Context Protocol (MCP) server designed to empower your AI Agents with context-awareness, safe execution sandboxes, and dedicated thought logs.
      -

    • Agentic Vault

      AliProgrammin
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that lets AI agents call APIs without ever seeing the credentials, using a local encrypted vault and per-secret allowlist policies for HTTP requests and subprocess environment variables.
      1
      AGPL 3.0

    • credential-broker-mcp

      SarutobiSasuke8
      A
      license
      Not graded
      quality
      C
      maintenance
      A local-first MCP server that lets AI agents use gated APIs without holding keys, enforcing declarative policies, injecting secrets server-side, and auditing access without content.
      2
      Apache 2.0

    • OpenAPI to Model Context

      gujord
      A
      license
      Not graded
      quality
      D
      maintenance
      A proxy server that bridges AI agents and external APIs by dynamically translating OpenAPI specifications into standardized MCP tools, enabling seamless interaction without custom integration code.
      69
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool maps to a distinct resource and action: products, budget read/write, alerts, balance, transactions, and session lifecycle/telemetry. The closest pairs (get_balance vs. get_budget, usage_alerts vs. session_usage) have clearly different described purposes, so an agent can reliably select among them.

    Naming Consistency4/5

    All tools use the nexalayer_ prefix and snake_case, with a mostly consistent verb_noun pattern such as list_products, set_budget, and create_session. Three read tools use noun phrases instead (usage_alerts, session_health, session_usage), which is a minor deviation but still readable and predictable.

    Tool Count5/5

    Eleven tools is well-scoped for a network session and billing domain. Each tool covers a needed operation across catalog, budget, alerts, billing, and session controls, with no obvious redundancy or trivial filler.

    Completeness3/5

    Core billing/budget operations and session create/rotate/terminate plus health/usage reads are covered. However, there is no list_sessions or get_session tool, so an agent cannot enumerate or recover session IDs for existing sessions, which is a notable gap for autonomous session management.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources