alethia-mcp
OfficialRelated Servers
Alternatives to alethia-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables transparent MCP proxying with a hash-chained effect ledger, classifying agent actions by reversibility, enforcing approval gates, and dry-run previews of sessions.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP clients to screen proposed actions, enforce deterministic policies and limits, and produce tamper-proof signed audit receipts before any external side effect is executed.4 npmMIT
- AlicenseAqualityCmaintenanceEnables policy-governed MCP interactions with deterministic authorization, tenant isolation, minimized PII exposure, and human approval gates for sensitive mutations, while producing structured audit events.3MIT
- FlicenseNot gradedqualityBmaintenanceEnforces default-deny policies, budgets, and tamper-evident audit logging for MCP tool calls before they reach upstream 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 gradedqualityAmaintenanceMCP server that gates agent tool calls by normalizing intent, denying unknown/unattended destructive actions, and requiring HITL prove approval for high-risk operations. It maintains an append-only hash-chained Action Ledger and exposes gate_check and ledger_verify tools without ever executing tools.MIT
TDQS
Scored across 15 tools
Each tool has a clearly distinct purpose: executing tests, compiling, monitoring, UI control, safety override, capturing state, JS query, audits, session export, parallel execution, demo server, test proposal, safety assertion, and cockpit control. Even related tools like audit_wcag and audit_nist target different standards.
All tools share the 'alethia_' prefix and use snake_case, making the pattern highly predictable. However, a few names (status, screenshot, eval) are nouns or abbreviations rather than verbs, which slightly deviates from a strict verb_noun convention.
With 15 tools, the server sits at the upper boundary of a well-scoped set. Each tool addresses a distinct need in the automation workflow, though some are auxiliary (e.g., cockpit controls, demo server) and could be trimmed without losing core functionality.
The tool set provides comprehensive coverage for the stated purpose: compile/preview, execute, observe (screenshot/eval), audit (WCAG/NIST), safety verification, session export, and parallel execution. There are no obvious dead ends or missing critical operations.