cedulon
Related Servers
Alternatives to cedulon
No user-submitted related servers found.
Related Servers
- 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.-
- AlicenseAqualityAmaintenancePost-quantum, tamper-evident receipts for consequential agent actions. Provides tools for auditing, gating decisions, and egress classification with quantum-hardened security.7Apache 2.0
- FlicenseNot gradedqualityDmaintenanceProvides MCP tools to enforce spend policies (allow, deny, step-up, allowlist) on agent wallets with an immutable audit trail.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to pay x402 endpoints on Cardano through a policy-gated wallet with spend caps, payee allowlists, human approval, and an audit log.Apache 2.0
- FlicenseNot gradedqualityBmaintenanceProvides policy-driven runtime authorization and security evaluation for MCP-based agents, including MCP streaming HTTP gateway, mock MCP servers, deterministic agent demos, and audited tool invocation with redacted PostgreSQL audit chains.-
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.