Atlas
Related Servers
Alternatives to Atlas
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to run side-effecting actions like tool calls, file writes, and payments only when each exact set of arguments is covered by a signed, scoped, single-use permit verified server-side, with high-risk actions requiring human sign-off and every allow/deny recorded in a tamper-evident hash-chained ledger.4-
- AlicenseNot gradedqualityCmaintenanceProvides permission gates and tamper-evident audit logging for AI agent tool executions, with declarative policies, consent ladders, and hash-chained verification.MIT
- AlicenseAqualityBmaintenanceOwner-signed authorization before agent actions. Hosted Vizier v0.5.13 MCP: https://vizier.agendamcp.dpdns.org/mcp. ALLOW/BLOCK/REVIEW; anonymous calls never ALLOW. Your integration enforces the decision. SDK v0.5.13: https://www.npmjs.com/package/@agenda-intelligence/vizier-sdk. Grants are signed; legacy receipts are unsigned. Python stdio is a separate catalog.3MIT
- AlicenseBqualityBmaintenanceEnables AI agents to execute actions under an accountability layer with identity passports, mandates, a permission gate, and a tamper-evident journal, while requiring human confirmation for irreversible operations.75AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables agents to route every action through a pre-execution gate that returns allow, escalate-to-human, or deny verdicts, backed by deterministic hard-rule blocks plus probabilistic gray-zone scoring, and to run a resumable orchestration loop covering routing, quality gates, stop-loss, acceptance, and escalation. Every decision, arbitration between conflicting agents, and human approval is written to an append-only hash-chained, Ed25519-signed ledger that can be postmortemed, calibrated, alert-scanned, and exported as offline verification bundles or OTel spans.1MIT
- AlicenseNot gradedqualityBmaintenanceProvides a governed execution boundary for AI agents, enforcing deterministic policy, one-shot human approvals, and signed receipts for MCP tool effects.MIT
TDQS
Scored across 4 tools
Each tool maps to a distinct stage of the authorization lifecycle: request a decision, report an effect, query a receipt, and verify the audit log. There is no plausible way to confuse atlas_authorize with atlas_commit_effect or atlas_receipt_status given their descriptions.
All four tools use a uniform atlas_ prefix with a clear verb_noun pattern (authorize, commit_effect, receipt_status, verify_audit). Naming is predictable and self-describing.
Four tools exactly cover the permit-check-commit-verify loop without redundancy. Nothing feels padded or missing at the surface level.
The core consequential-action flow (authorize, commit, status, audit verification) is fully covered, including escalation and revocation states. Minor gaps exist for discovery operations like listing receipts or checking pending approvals in bulk, which agents would have to work around with known receipt_ids.