UNITARES
Related Servers
Alternatives to UNITARES
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceRuntime policy enforcement for AI agents. Evaluate every agent action against your organization's policies before execution, with observe and enforce modes.11MIT
- FlicenseAqualityFmaintenanceProvides policy-based access control, incident tracking, and compliance monitoring to govern AI agent behavior. It enables organizations to enforce security rules and maintain audit trails by validating agent actions against trust levels and pattern-based policies.61-

Rigour MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to self-govern by scanning code for hardcoded secrets, structural violations, and AI drift in real-time, providing fix packets for automatic remediation.27MIT- AlicenseBqualityBmaintenanceProvides AI governance and action-assurance primitives, enabling trust scoring, policy-based allow/deny decisions, risk assessment, EU AI Act compliance checks, and an emergency kill-switch for autonomous agents.627 npmMIT
- AlicenseNot gradedqualityBmaintenanceBehavioral governance layer for AI assistants that monitors for hallucination, inconsistency, and unsafe reasoning patterns while managing stateful AI sessions.100 npmMIT

@vorionsys/mcp-serverofficial
AlicenseAqualityBmaintenanceMCP server for AI-agent governance using trust scoring, behavioral signals, and pre-flight action checks.1013 npm1Apache 2.0
This server cannot be deployed
TDQS
Scored across 14 tools
Most workflow tools are distinct and well-described, such as request_review versus consult and record_result versus store_finding. However, the generic knowledge tool duplicates the search/store/update surfaces of search_shared_memory, store_finding, and update_finding without clear guidance on when to prefer the specialized wrappers, creating real selection ambiguity.
Most tools follow a readable verb_noun snake_case pattern like record_result, start_session, and store_finding. The pattern is broken by knowledge, identity, consult, and self_recovery, which are bare nouns/verbs or compound nouns, making the naming style mixed but still understandable.
14 tools is a reasonable size for a broad agent lifecycle server, and most tools represent distinct concerns. The count is slightly heavier than necessary because the knowledge tool overlaps with three specialized wrappers, but overall it is still well-scoped.
The set covers session start, state read/update, result recording, finding storage/update/search, structured review, consultation, health checks, identity, and self-recovery—a fairly complete operational lifecycle. Minor gaps include no explicit session end/close tool and no direct result retrieval, but these are likely workaroundable.