Cedulon
NPM · @CEDULON/MCP-SERVER · SCANNED SEP 21
Policy-gated agent spend with signed receipts and rail-extract audit
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 103 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to dogrucanemek-alt/cedulon). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 9 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 854 tokens (~170/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 65% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Cedulon MCP server?
Cedulon runs locally as an npm package, launched with npx -y @cedulon/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @cedulon/mcp-server
claude mcp add dogrucanemek-alt-cedulon -- npx -y @cedulon/mcp-server
{
"mcpServers": {
"dogrucanemek-alt-cedulon": {
"command": "npx",
"args": [
"-y",
"@cedulon/mcp-server"
]
}
}
} {
"servers": {
"dogrucanemek-alt-cedulon": {
"command": "npx",
"args": [
"-y",
"@cedulon/mcp-server"
]
}
}
} codex mcp add dogrucanemek-alt-cedulon -- npx -y @cedulon/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dogrucanemek-alt-cedulon": {
"type": "local",
"command": [
"npx",
"-y",
"@cedulon/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add dogrucanemek-alt-cedulon --command npx --arg -y --arg @cedulon/mcp-server
mcp_servers:
dogrucanemek-alt-cedulon:
command: "npx"
args: ["-y", "@cedulon/mcp-server"] {
"McpServers": {
"dogrucanemek-alt-cedulon": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@cedulon/mcp-server"
]
}
}
} assistant mcp add dogrucanemek-alt-cedulon -t stdio -c npx -a -y @cedulon/mcp-server
{
"mcpServers": {
"dogrucanemek-alt-cedulon": {
"command": "npx",
"args": [
"-y",
"@cedulon/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.13.0 → 0.13.1 functional
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/@cedulon/mcp-server@0.13.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | dogrucanemek-alt/cedulon |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/dogrucanemek-alt/cedulon/.github/workflows/release.yml@refs/tags/v0.13.1 |
| Rekor log index | 2792275727 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c2b9abb97ee61be625f2c39366918256d4d41c4ee3f068f28733ae30ab970fafa9f557dfbdc4ef26134fd23459de9d7d7e4f33f5e12ab4dfa17593cd8 |
Background: How many MCP packages publish verified provenance →
Dependencies 103 packages
| Packages resolved | 103 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cedulon_audit ~521
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).
| Name | Type | Req | Description |
|---|---|---|---|
| extraSettlements | array | – | Optional extra extract rows, used to inject a bypass settlement in tests |
| extract | object | – | A signed rail extract you were presented with: { body: { accountId, railId, windowStartMs, windowEndMs, settlements: [{ ref, amount, currency, timestampMs }], clockSkewMs? }, signature, publicKeyPem… |
| issuerTrust | object | – | Issuer key(s) you hold out of band: { publicKeyPem: string | string[] }. Without it the audit checks this server's records against this server's own key. |
| manifest | object | – | A Trade Manifest you were presented with. Omit for a no-manifest deployment. Present without manifestTrust is unauthenticated-manifest. |
| manifestTrust | object | – | Manifest publisher key(s) you hold out of band: { publicKeyPem: string | string[] } |
| payeeTrust | object | – | Payee keys you hold out of band, keyed by payee: { "payee-1": publicKeyPem } |
| trust | object | – | Rail key you hold out of band: { publicKeyPem, accountId?, railId?, windowStartMs?, windowEndMs? } |
| witnessTrust | object | – | Transparency log key you hold out of band: { publicKeyPem: string | string[] } |
No output schema declared.
No examples provided.
cedulon_export_ledger ~49
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cedulon_spend ~87
Policy-gated spend on the mock rail. Allow returns a signed COSE receipt JSON. Deny returns the fail-closed reason.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Integer amount as a decimal string |
| currency | string | yes | – |
| nonce | string | yes | – |
| payee | string | yes | – |
| tool | string | – | Calling tool name recorded on the request |
No output schema declared.
No examples provided.
cedulon_status ~24
Server version, policy summary, receipt count, and chain head hash.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cedulon_verify_receipt ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| coseHex | string | – | – |
| counterCoseHex | string | – | – |
| expectIssuerKeyPem | string | – | Issuer key you hold out of band. Omit and the check is self-referential. |
| expectPayeeKeyPem | string | – | Payee key you hold out of band, for the countersignature. |
| payeePublicKeyPem | string | – | – |
| publicKeyPem | string | – | – |
| receipt | object | – | Full SignedReceipt object from cedulon_spend |
No output schema declared.
No examples provided.
What is the Cedulon MCP server?
Cedulon is an MCP server listed in the public MCP registry as io.github.dogrucanemek-alt/cedulon. Policy-gated agent spend with signed receipts and rail-extract audit. This page covers its npm package (@cedulon/mcp-server).
Is the Cedulon MCP server safe to use?
Cedulon scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Cedulon MCP server expose?
Cedulon exposes 5 tools: cedulon_spend, cedulon_audit, cedulon_verify_receipt, cedulon_export_ledger, cedulon_status. Their descriptions and schemas cost roughly 854 tokens of context every time the server is loaded.
Is the Cedulon MCP server still maintained?
Cedulon is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Cedulon MCP server under?
Cedulon declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.