Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Cedulon

NPM · @CEDULON/MCP-SERVER

Policy-gated agent spend with signed receipts and rail-extract audit

Available components

−1 this week 91 Trust /100

Last scanned (18 hours ago)

Scores higher than 94% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

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
  • 30 of 100 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 4 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 858 tokens (~171/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 1 Nov 26 +25
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Stability: 0.97 → pass security
    • Dependency health: unverified → 0.88 ▲ functional
  • 31 Oct 26 −25
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: 0.88 → unverified ▼ functional
    • Stability: pass → 0.97 functional
    • Package version: 0.16.0 → 0.17.0 functional
  • 30 Oct 26 −1

    No change was recorded against any check on this day. Supply Chain Security went from 99 to 98.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Supply Chain Security went from 98 to 99.

  • 26 Oct 26 0
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.15.0 → 0.16.0 functional
  • 25 Oct 26 0
    • Stability: 0.97 → pass security
  • 24 Oct 26 0
    • Stability: pass → 0.97 functional
  • 18 Oct 26 +1
    • Known CVEs: partial → pass ▲ security
    • Stability: 0.97 → pass security
    • Dependency health: partial → 0.87 functional
Diagnostics

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 5 Nov 2026 · Analysed npm/@cedulon/mcp-server@0.17.0

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.17.0
Rekor log index 3614162476
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:d133c61e4611ced7dbb24746224b2f459d2813cf8a8e232992b6d721526babd35a65bd16e383e07e4842c3c5ed2296cb62653a9b1d7b47a7d266c560b

Background: How many MCP packages publish verified provenance →

Dependencies 100 packages
Packages resolved 100
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~858 tokens

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 →

Tool Tokens
cedulon_audit ~525

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).

NameTypeReqDescription
extraSettlementsarray–Optional extra extract rows, used to inject a bypass settlement in tests
extractobject–A signed rail extract you were presented with: { body: { accountId, railId, windowStartMs, windowEndMs, settlements: [{ ref, amount, currency, timestampMs }], clockSkewMs? }, signature, publicKeyPem…
issuerTrustobject–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.
manifestobject–A Trade Manifest you were presented with. Omit for a no-manifest deployment. Present without manifestTrust is unauthenticated-manifest.
manifestTrustobject–Manifest publisher key(s) you hold out of band: { publicKeyPem: string | string[] }
payeeTrustobject–Payee keys you hold out of band, keyed by payee: { "payee-1": publicKeyPem }
trustobject–Rail key you hold out of band: { publicKeyPem: string | string[], accountId?, railId?, windowStartMs?, windowEndMs? }
witnessTrustobject–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.

NameTypeReqDescription
amountstringyesInteger amount as a decimal string
currencystringyes–
noncestringyes–
payeestringyes–
toolstring–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.

NameTypeReqDescription
coseHexstring––
counterCoseHexstring––
expectIssuerKeyPemstring–Issuer key you hold out of band. Omit and the check is self-referential.
expectPayeeKeyPemstring–Payee key you hold out of band, for the countersignature.
payeePublicKeyPemstring––
publicKeyPemstring––
receiptobject–Full SignedReceipt object from cedulon_spend

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add dogrucanemek-alt-cedulon -- npx -y @cedulon/mcp-server
Common questions

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 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 858 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 5 November 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.

What did VerifyMCP test on the Cedulon MCP server?

VerifyMCP ran 16 checks on Cedulon, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.