cedulon
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cedulon_spendA | Policy-gated spend on the mock rail. Allow returns a signed COSE receipt JSON. Deny returns the fail-closed reason. |
| cedulon_auditA | Reconcile the in-process receipt chain and checkpoint against the rail extract: this server's own ledger, or a signed extract you present. Returns audit: balanced or findings, names the account, rail and window it was computed over (scope) when an extract declared one, and counts the class every receipt and row landed in (counts). |
| cedulon_verify_receiptA | Verify a spend receipt COSE_Sign1 (and payee countersignature when present). Supply expectIssuerKeyPem to check it against a key you already hold; without one the receipt is only checked against the key it carries, which any key satisfies. |
| cedulon_export_ledgerA | Export receipts, checkpoint, and rail extract in the same JSON shape as npm run demo:export, with the findings, guarantee and counts of the audit over this server's own ledger. |
| cedulon_statusA | Server version, policy summary, receipt count, and chain head hash. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.