All servers / Payments / Cedulon MCP server
Cedulon MCP server
Local stdio MCP server for policy-gated Cedulon spend and audit.
Tested by ConnectATDScore 83 out of 100. Tested 2026-11-19 on package version 0.18.0. Package: @cedulon/mcp-server · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 17 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (5.4 seconds including download)
- Tools offered: 5
- Last published: 2026-11-12
- Weekly downloads (npm): 497
- License: Apache-2.0 · Direct dependencies: 8
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
cedulon_spend2 of 5 parameters describedPolicy-gated spend on the mock rail. Allow returns a signed COSE receipt JSON. Deny returns the fail-closed reason.
cedulon_audit8 of 8 parameters describedReconcile 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_receipt3 of 7 parameters describedVerify 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_ledgerno parametersExport 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. A stored checkpoint whose encoding is not strict hex reports hash: null.
cedulon_statusno parametersServer version, policy summary, receipt count, and chain head hash.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.