Skip to main content
Glama

Related Servers

Alternatives to NyxID

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Self-hosted MCP gateway that registers upstream MCP servers and fronts them behind one governed Streamable HTTP endpoint: per-tool access control by caller API key, guardrails over tool arguments and results, rate limits, and usage logs. The same Rust gateway also proxies LLM and A2A agent traffic.
      4
      1
      157
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted MCP gateway that connects Claude, ChatGPT, and other AI agents to 20+ enterprise tools (GitLab, Jira, Notion, Google Workspace, Slack, Grafana, …) with OAuth, audit logs, and zero data leaving your infrastructure
      -
    • A
      license
      A
      quality
      F
      maintenance
      A Model Context Protocol (MCP) server for authenticated REST APIs. Drop it into any project, point it at your API, and let AI agents call endpoints — with auto-login, 2FA support, Swagger spec fetch, and fuzzy endpoint search — all without writing a single line of auth code.
      3
      10 npm
      6
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      One local gateway for all your MCP servers — shared by every AI coding tool (Claude, Cursor, VS Code, Codex). Set up each server once; keys stay in the OS keychain; lazy discovery keeps agent context small. Local-first, open source.
      4
      2 npm
      219
      MIT
    • A
      license
      Not graded
      quality
      B
      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
    • A
      license
      C
      quality
      D
      maintenance
      Turn any REST API into an MCP server in one command. Point mcpify at an OpenAPI spec and every endpoint becomes a tool your AI agent (Claude, Cursor, Windsurf) can call — zero glue code, always in sync with the spec.
      3
      5
      MIT

    TDQS

    A4.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool addresses a distinct function: token exchange, service discovery, proxied requests, and human approval. No two tools could be confused for the same purpose.

    Naming Consistency5/5

    All tools follow the nyx_verb_noun pattern consistently (exchange_identity, list_services, proxy_request, request_approval). No mixing of styles.

    Tool Count5/5

    Four tools is well-scoped for an identity-and-proxy server; each tool fills a necessary role without redundancy or excessive granularity.

    Completeness4/5

    The set covers the core lifecycle: identity exchange, service discovery, proxy calling, and human approvals. Minor gaps like token revocation or listing active approvals exist but are workable.

    Maintenance

    ActivityActive
    ResponsivenessResponsive