Last updated 27 August 2026.
The Cedulon MCP server runs on your own machine and speaks to your MCP client over standard input and output. We do not host it, we do not operate a service behind it, and there is no endpoint of ours for it to talk to.
Nothing. We receive no data from the server, because the server sends none. This is not a policy commitment we ask you to take on trust: the published package and the seven packages it depends on contain no HTTP client, no socket, and no telemetry, and its only dependency outside the project is the official Model Context Protocol SDK. The source is public and the dependency list is short enough to read.
In memory, for the lifetime of the process: the spend requests made in the session (amount, currency, payee, a nonce, and the name of the calling tool), the signed receipts derived from them, the epoch checkpoint, and the policy limits you configured. Ending the process discards all of it.
By default, nothing. If you set the CEDULON_STATE_PATH
environment variable, the ledger described above is written as JSON to
that path, on your machine, so that a session can resume. You choose
the path, you can delete the file at any time, and we never see it.
None. No analytics, no crash reporting, no update check, no content delivery network, no advertising, and no data sharing of any kind. The server has no mechanism to do these things.
In-memory state lasts as long as the process. A state file, if you enabled one, lasts until you delete it. We hold nothing, so we retain nothing and there is nothing for us to delete on your behalf.
Cedulon is a developer tool and is not directed at children. It collects no data from anyone, including children.
The repository also contains an optional demonstration that reads a public blockchain RPC endpoint you supply, to reconcile a receipt chain against a real settlement window. It is read-only, it holds no wallet and no key, and it is not part of the packaged MCP server or the desktop extension. It runs only if you clone the repository and invoke it yourself with an endpoint of your choosing.
If this policy changes, the date above changes with it, and the change is visible in the repository history alongside the code it describes.
Emek Can Dogru — e.dogru@conarium.dev. Security reports and privacy questions both reach the same address.