Skip to main content
Glama
TravT

Aegis-Sovereign MCP Server

by TravT

Related Servers

Alternatives to Aegis-Sovereign MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      C
      maintenance
      Enables AI agents to discover and query enterprise knowledge documents and business metrics through standardized MCP tools, supporting retrieval, structured sales/order analysis, anomaly scanning, and data lineage lookups.
      12
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible agents such as Claude and Cursor to retrieve permission-aware, structured context from local or hosted data stores. Exposes tools for semantic search, entity and relationship lookup, memory access, context pack compilation, source attribution, and retrieval explanation.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to securely discover, invoke, and manage tools through a hardened MCP endpoint with protections like injection detection, circuit breakers, retry backoff, response caching, context-window limiting, and state snapshots.
      1 npm
      MIT

    TDQS

    B3.1/5.0

    Scored across 7 tools

    Disambiguation3/5

    Most tools target distinct operations (scan, status, optimize, search, dossier, route, inspect), but sovereign_optimize_context, sovereign_search_vault, and sovereign_route_and_analyze all involve retrieval/analysis and could be confused for similar high-level queries. The descriptions help, but the boundaries between 'optimize context', 'search vault', and 'route and analyze' are not immediately crisp.

    Naming Consistency4/5

    All tools share the 'sovereign_' prefix and use verb_noun or verb_phrase patterns (scan_onboarding_radar, node_status, optimize_context, search_vault, get_entity_dossier, route_and_analyze, inspect_archive). Minor inconsistency: 'sovereign_node_status' lacks a verb, while others have explicit verbs, but overall the pattern is predictable.

    Tool Count4/5

    Seven tools is a reasonable count for a specialized knowledge-management/retrieval server. The scope is broad (onboarding, search, routing, archive inspection, entity dossiers), but each tool covers a distinct capability without feeling bloated.

    Completeness3/5

    The server covers discovery, search, retrieval, routing, archive inspection, and node health, but lacks obvious lifecycle operations like adding/updating/deleting documents or managing the vault corpus. The inspect_archive tool has some maintenance actions (relocate_prefix, purge_prefix), but there is no clear ingest/write tool, leaving a notable gap for a knowledge vault server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues