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
- AlicenseNot gradedqualityBmaintenanceEnables 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.MIT
- FlicenseNot 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.-
- 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.-
- AlicenseAqualityAmaintenanceSigned receipts for agent actions and a read-only-allowlist decision gate, as an MCP server. Ed25519, plus ML-DSA-65 when the post-quantum backend is available. gate_decision returns ALLOW, DENY or ESCALATE from action names and does not observe or block anything. verify_receipt takes expected_kid to pin which key signed. Seven tools.7Apache 2.0
- FlicenseNot gradedqualityDmaintenanceProvides MCP tools to enforce spend policies (allow, deny, step-up, allowlist) on agent wallets with an immutable audit trail.-
TDQS
Scored across 5 tools
Each tool maps to a distinct operation: status for server health and context, spend for initiating a payment, audit for reconciliation, verify_receipt for signature validation, and export_ledger for extracting data. There is no meaningful functional overlap between any pair.
All names use lowercase snake_case and share the cedulon_ prefix, which is a solid convention. However, the action pattern is slightly inconsistent: status and audit are noun-style, while spend, verify_receipt, and export_ledger are verb or verb_noun style.
Five tools is well-scoped for a focused payment/audit server. Each tool has a clear role—information, spend, verification, audit, export—and none feels redundant or excessive.
The tool set covers the core workflow: spend creates a receipt, verify_receipt validates it, audit reconciles the ledger or a presented extract, and export_ledger provides data portability. Status supplies the necessary server-level context, so there are no obvious dead ends for the stated domain.