Skip to main content
Glama
prince-rai88

Aegis

by prince-rai88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Aegis

No user-submitted related servers found.

    Related Servers

    • GUARDIAN MCP

      brundhas26
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables secure runtime mediation of tool requests from MCP-connected AI agents, enforcing least-privilege policies, validating intent and inputs, detecting multi-step attacks and information leaks, and supporting explainable decisions, audit trails, and human approval for sensitive actions.
      MIT

    • inkog

      inkog-io
      A
      license
      A
      quality
      B
      maintenance
      Security co-pilot for AI agents. Scans for vulnerabilities like prompt injection, infinite loops, and token bombing in AI Agents, audits MCP servers, verifies AGENTS.md governance, and generates EU AI Act compliance reports.
      10
      160 npm
      3
      Apache 2.0

    • EnterpriseRBACLeastPrivilegePo

      alphaparkinc
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables analysis of historical agent tool-call audit logs to detect over-permissioned wildcards, synthesize strict least-privilege JSON security boundary policies, and quantify attack surface and blast-radius reduction.
      8
      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

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: connect_tool adds capabilities, get_capability_graph inspects state, detect_attack_paths analyzes for risks, and apply_policy_fix remediates. There is no overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscore separation: connect_tool, get_capability_graph, detect_attack_paths, apply_policy_fix. The style is uniform and predictable.

    Tool Count5/5

    Four tools is well-scoped for a focused security/capability management server. Each tool covers a necessary step and none feel extraneous.

    Completeness4/5

    The set covers the core lifecycle: connect, inspect, detect, and remediate. The only minor gap is the lack of a direct 'disconnect_tool' independent of attack-path remediation, but apply_policy_fix effectively serves that purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources