Verax
OfficialRelated Servers
Alternatives to Verax
- AlicenseAqualityBmaintenanceSelf-hosted governance layer between an AI assistant and your data: allow/deny policy, deterministic PII masking, row caps, and a hash-chained audit log with an Ed25519-signed receipt for every access, verifiable offline.4955 npm3MIT
- AlicenseAqualityBmaintenancePolicy-gated agent spend with signed receipts and rail-extract audit: a fail-closed gate issues a COSE receipt for every allowed payment, and the audit reconciles those receipts against a rail extract so a settlement with no receipt is named rather than assumed. It settles on a mock rail, holding no wallet and signing no transaction.51Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to store and retrieve provenance-aware facts with source, age, and boundaries, supporting search, read, propose, and local telemetry via MCP tools.426 npmApache 2.0
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides a governed execution boundary for AI agents, enforcing deterministic policy, one-shot human approvals, and signed receipts for MCP tool effects.MIT
- AlicenseNot gradedqualityBmaintenanceProvides a policy-controlled MCP gateway that lets agents invoke tools with explicit policies, bounded execution, scoped visibility, and decision receipts.MIT
- AlicenseNot gradedqualityBmaintenanceEnables any MCP client to route an agent's tool calls through Abhed's action gate, receiving allowed outputs, waiting for human approval on held actions, or errors naming the rule that blocked them. Every decision is recorded on a hash-chained, Ed25519-signed ledger.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to safely call MCP tools through a security gateway that enforces per-role authorization and least-privilege tool scoping.1-
- AlicenseNot gradedqualityCmaintenanceEnables LLM agents to safely invoke enterprise MCP tools under an enforceable guard that applies allowlist policies, caller roles, parameter restrictions, human confirmation for destructive operations, and a correlated JSONL audit log.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to govern downstream tool servers by enforcing default-deny authority and attestation on every tool call, with live monitoring, approval, and mid-session revocation.3Apache 2.0
TDQS
Scored across 6 tools
Each tool targets a distinct resource and action: memory.get/put, message.send/read, spend authorization, and audit.explain. The descriptions reinforce clear boundaries, and no two tools appear interchangeable.
Five of six tools follow a consistent namespace.verb pattern (memory.get, memory.put, message.send, message.read, audit.explain). The lone bare verb 'spend' is a minor but noticeable deviation from the otherwise predictable convention.
Six tools is well-scoped for a local policy-gated agent body covering memory, messaging, spend authorization, and audit. Each tool earns its place without obvious redundancy.
The core lifecycle is partly covered: memory can be stored and recalled, messages can be queued and read, spending can be authorized, and decisions can be audited. However, there are notable gaps such as no memory listing or deletion, no message acknowledgement or inbox clearing, and no ledger query beyond single-ref lookup.