Aegis-Sovereign MCP Server
Related Servers
Alternatives to Aegis-Sovereign MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to access a local-first personal context and memory layer through MCP tools for bootstrapping user context, semantically searching Markdown vault knowledge, reading files, listing topics, and adding controlled memories. It provides deterministic context retrieval, provenance-cited vector search, and secure vault operations while keeping data local and model-independent.6MIT
- FlicenseAqualityCmaintenanceEnables 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-
- AlicenseNot gradedqualityCmaintenanceEnables agents to run hybrid retrieval, build token-budgeted attributed context packs, answer questions with citation and groundedness-gated release, explore temporal graph entities, evaluate claim support, and ingest screened, embedded documents through typed MCP tools.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to query a repository's living, versioned knowledge graph through 11 MCP tools, so they can search code, inspect node, file and community context, trace paths between routes and tables, run impact analysis, and review what changed between versions.47 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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.1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to securely search and ingest corporate documents via MCP, offering hybrid retrieval, PII sanitization, role-based access control, and citation validation.MIT
TDQS
Scored across 7 tools
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.
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.
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.
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.