cedulon
Related Servers
Alternatives to cedulon
- AlicenseAqualityAmaintenanceEnables MCP-speaking agents to execute tool calls through an authorization gate, producing signed decision records and reconciled effect rows for accountability.6Apache 2.0
Related Servers
- AlicenseAqualityBmaintenanceEnables agent-initiated shielded ZEC payments under human policy with a hard per-call spending cap, recipient allow-list, and append-only viewing-key fingerprinted audit log. Chain operations are mocked first, with live light-wallet adapter stubbed and refused at startup.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to inspect, check, and audit signed offline spending authorizations, and to issue hash-chained receipts for each action taken against them. Enforces per-transaction, total, expiry, merchant, and human-approval constraints, returning allow, needs_human, or deny with the specific failing constraint.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceDeterministic, auditable payment policy enforcement for AI agents. It provides pre-action authorization with scopes, budgets, allowlists, and signed mandates via an MCP server.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to propose wallet payments while a local, human-authored policy decides whether each transaction is approved, requires human confirmation, or is refused, and records every decision in a signed, append-only ledger.-
- AlicenseNot gradedqualityBmaintenanceEnforces verifiable authorization, budgets, approvals, and audit trails between an agent and merchant/payment MCP servers, so that the legality of an entire transaction — not just a single call — is checked before money moves. Adds default-deny policy, two-phase budget reserve/commit, action-bound approvals, transaction guards against double-charging or unpaid fulfillment, result sanitization, and tamper-evident hash-chain evidence.2MIT
- AlicenseAqualityAmaintenanceRead-only checks for money that agents move. verify_receipt: schema, Ed25519 signature, mandate expiry, amount = quantity x unit_price, refund not above payment. audit_spend: duplicate charges, price escalation, failed-but-billed, runaway loops, missing refunds, model overpay, budget breaches - three separate amounts, never one. reserve_report: NAV with an evidence hash per line; refuses a backing5Apache 2.0
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: audit reconciles the ledger, export serializes state, spend creates a receipt, status reports server metadata, and verify checks receipt signatures. The potential overlap between audit and export is handled by descriptions, with export explicitly packaging audit findings rather than replacing audit.
All names use the consistent cedulon_ snake_case prefix, making the set easy to scan. The suffixes mix verb forms (audit, spend, status) with verb_noun forms (export_ledger, verify_receipt), but this is a minor deviation rather than a confusing convention.
Five tools is well-scoped for a focused receipt-chain and mock-rail auditing server. Each tool covers a necessary lifecycle step without obvious redundancy.
The surface covers core operations: spend, verify, audit, export, and status, with export serving as the main access path for receipts and checkpoints. Minor gaps remain, such as no explicit list-receipts or direct checkpoint lookup, but agents can work around this through export.