Skip to main content
Glama
getaegis

Aegis

by getaegis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Aegis

No user-submitted related servers found.

    Related Servers

    • SecretVault MCP

      itsaygea
      A
      license
      Not graded
      quality
      B
      maintenance
      Bounded egress gateway & secret proxy for AI agents and applications, enabling safe credential injection into upstream requests while keeping raw secrets out of LLM prompt contexts.
      15 npm
      MIT

    • Access

      Scottpedia0
      A
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted credential store and API proxy for AI agents. One Bearer token, all your services. Handles OAuth refresh, encrypted storage, audit logging, and per-agent permissioning.
      125 npm
      MIT

    • AI Service Gateway MCP

      Yormede
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to securely access authenticated services (HTTP, SSH, SMTP) without exposing secrets, by acting as a server-side proxy that injects authentication.
      MIT

    • agent-auth

      ex-nihilo-labs
      A
      license
      Not graded
      quality
      D
      maintenance
      Zero-knowledge credential injection for AI agents. Your agent authenticates to websites and APIs without ever seeing a password, TOTP code, or API key.
      10 npm
      1
      MIT

    • keywarden

      DINAKAR-S
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to make authenticated API calls and run commands with secrets injected, while keeping credentials completely hidden from the model, with policy enforcement, grants, and audit logging.
      6
      MIT

    • agent-sudo-mcp

      Kisyntra
      A
      license
      A
      quality
      A
      maintenance
      Local zero-trust permission gateway for AI agents. Enforces policy-based tool authorization, human approvals, scoped permissions, and cryptographically verifiable audit logs.
      4
      5
      Apache 2.0
    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.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: health monitoring, service listing, and proxying requests. There is no overlap in functionality, and an agent can easily differentiate between them based on their specific roles.

    Naming Consistency5/5

    All tool names follow a consistent 'aegis_' prefix with descriptive snake_case suffixes (health, list_services, proxy_request). This pattern is uniform across all tools, making them predictable and easy to understand.

    Tool Count3/5

    With only 3 tools, the server feels minimal for a service management system like Aegis. While the tools cover basic operations, the scope might be too thin, potentially lacking advanced management features like service registration or configuration updates.

    Completeness3/5

    The tools provide core functionality for health checks, service listing, and proxying requests, but there are notable gaps. For example, there are no tools for managing services (e.g., adding or removing services) or handling authentication configurations, which could limit agent workflows in a service management context.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources