mcp-vaara
OfficialRelated Servers
Alternatives to mcp-vaara
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides permission gates and tamper-evident audit logging for AI agent tool executions, with declarative policies, consent ladders, and hash-chained verification.MIT
- AlicenseNot gradedqualityAmaintenanceTamper-evident audit trail for AI agent tool calls. Cryptographically signed, hash-chained records that prove what your agents did.311 npmMIT
- AlicenseBqualityAmaintenanceA governance proxy for AI tools — every MCP/agent tool call is policy-gated, secret-redacted, and written to a hash-chained, offline-verifiable audit trail.13MIT

ERDL Guardofficial
AlicenseNot gradedqualityAmaintenanceEnforces deterministic policy decisions on AI agent tool calls, supporting allow, deny, correct, escalate, and human review actions with verifiable audit receipts.11 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables governed tool-calling agents with policy decisions, optional human approval, hash-chained audit logging, and deterministic evaluation.MIT

agentguardofficial
AlicenseNot gradedqualityAmaintenanceEnforces policy controls for AI agents, including spend limits, action approvals, kill switch, scoped credentials, dry-run diffs, loop prevention, and auditable hash-chained logs.MIT
TDQS
Scored across 4 tools
vaara_check and vaara_intercept overlap substantially—both classify, score risk with conformal prediction, and return allow/deny/escalate. The descriptions explicitly differentiate them (check = no audit recording; intercept = full audit trail), which resolves most confusion, but the boundary still requires careful reading.
All four tools follow a strict 'vaara_' prefix plus clear verb_noun pattern (check, intercept, report_outcome, verify_receipt). The convention is predictable and readable throughout.
Four tools is a tight, well-scoped set for a risk-scoring and governance service, and each has a distinct role in the decision lifecycle. Slightly thin but no tool feels redundant or filler.
The set covers scoring, interception with audit recording, outcome feedback, and receipt verification, forming a closed loop. A read/list tool for the audit trail itself is absent, a minor gap agents could work around via verify_receipt.