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.

io.github.Anselmoo/mcp-ooxml-ledger

OCI · GHCR.IO/ANSELMOO/MCP-OOXML-LEDGER:0.3.0 · 2 COMPONENTS

Edit Office documents and prove no edit went unrecorded

0 this week 50 Trust /100

Last scanned (2 hours ago)

Scores higher than 77% of OCI servers

Category Documents and Files

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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 52 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2201 tokens (~157/item across 14 items; 14 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 Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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 +1
    • Stability: 0.97 → pass security
  • 31 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 20 Oct 26 +1
    • Stability: 0.97 → pass security
  • 19 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.87 → pass security
  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 −3
    • Stability: pass → 0.80 functional
  • 13 Oct 26 +1
    • Stability: 0.97 → pass security
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 oci/ghcr.io/anselmoo/mcp-ooxml-ledger:0.3.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 14 exposed · ~1,510 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
apply_edits ~132

Apply a batch of edits to the document and record each one in the session's journal. ALL-OR-NOTHING: the document is written only if every edit applied, so a failed batch leaves the file byte-identical and journals nothing. `mode` 'tracked' emits Word revision marks a reviewer can see; 'direct' rewrites the text and is recorded in the ledger alone, which the receipt discloses. Seal the session with `commit_document`.

NameTypeReqDescription
authorstringyes–
editsarrayyes–
modestring––
session_idstringyes–
NameTypeReqDescription
appliedintegeryes–
baseline_digeststringyes–
document_digest_changedbooleanyes–
outcomesarrayyes–
partsarrayyes–
result_digest–yes–
revision_idsarrayyes–
session_idstringyes–

No examples provided.

close_document ~61

End a session and delete its working directory WITHOUT sealing a receipt. Refuses when the journal holds recorded operations unless `discard` is set — closing over them would throw away the accountability record.

NameTypeReqDescription
discardboolean––
session_idstringyes–
NameTypeReqDescription
closedbooleanyes–
journal_unreadable–––
operations_discarded–yes–
removed_directorystringyes–
session_idstringyes–

No examples provided.

commit_document ~102

End a session by sealing its journal into a receipt, but only if the recorded operations account for every change to the document. If they do not, the commit is REFUSED. `force` overrides a failed gate VERDICT and the override is recorded in the receipt, where `verify` will surface it; it does not override a ledger that could not be read or replayed at all.

NameTypeReqDescription
forceboolean––
session_idstringyes–
NameTypeReqDescription
baseline_digeststringyes–
caveatstringyes–
documentstringyes–
forcedbooleanyes–
gatestringyes–
gate_failuresarrayyes–
noticesarrayyes–
operationsintegeryes–
receipt_pathstringyes–
result_digeststringyes–
session_idstringyes–
structural–yes–
visibility–yes–

No examples provided.

delete_paragraph ~207

Delete one whole paragraph and record it in the session's journal. Address it by `para_id` — the `w14:paraId` `find_text` returns — or by `para_index` TOGETHER WITH `para_hash`, because an index alone silently addresses a different paragraph once anything above it moves. `mode` 'tracked' marks the paragraph mark AND every run with `w:del`, so a reviewer can reject it back and nothing is actually removed; 'direct' removes it outright and is accounted for by the ledger alone, which the receipt discloses. Refused if the paragraph carries a section break, or holds an unaccepted revision by another author. Seal the session with `commit_document`.

NameTypeReqDescription
authorstringyes–
modestring––
note–––
para_hash–––
para_id–––
para_index–––
partstringyes–
session_idstringyes–
NameTypeReqDescription
after–yes–
baseline_digeststringyes–
before–yes–
document_digest_changedbooleanyes–
modestringyes–
note–yes–
opstringyes–
para_id–yes–
para_indexintegeryes–
partstringyes–
partsarrayyes–
result_digeststringyes–
revision_idsarrayyes–
session_idstringyes–

No examples provided.

describe_structure ~91

Report a session document's structure: which parts the digest covers, which it excludes, and the format's own units — paragraphs for docx, sheets for xlsx, slides (in <p:sldIdLst> order, never filesystem order) for pptx. Describes the session's working copy as opened; `verify` reports on the file on disk now.

NameTypeReqDescription
session_idstringyes–
NameTypeReqDescription
baseline_digeststringyesThe canonical digest of this document AS IT WAS WHEN THE SESSION WAS OPENED, and of the working copy these results were read from — not an attestation about the file on disk right now. Call `verify`…
documentstringyes–
document_may_have_changed_since_openbooleanyesTrue when the document FILE on disk no longer has the size and modification time it had when this session last touched it — so these results may describe a version that no longer exists. It reports w…
excluded_partsarrayyes–
included_partsintegeryes–
kindstringyes–
namestringyes–
paragraphs–––
partsintegeryes–
session_idstringyes–
sheets–––
slides–––
text_partsarrayyes–

No examples provided.

digest ~50

Compute a document's canonical digest — stable across a no-op Office save, and the key a receipt is stored under. Needs no session.

NameTypeReqDescription
documentstringyes–
include_partsboolean––
NameTypeReqDescription
canonstringyes–
digeststringyes–
documentstringyes–
kindstringyes–
namestringyes–
parts–––

No examples provided.

export_receipt ~60

Write this document's receipt out as one self-contained sidecar file — the thing you attach to a submission, commit to git, or register alongside a DOI.

NameTypeReqDescription
dest–––
documentstringyes–
overwriteboolean––
NameTypeReqDescription
bytesintegeryes–
caveatstringyes–
documentstringyes–
forcedbooleanyes–
gatestringyes–
operationsintegeryes–
pathstringyes–
result_digeststringyes–

No examples provided.

find_text ~214

Case-insensitive substring search over every text-bearing part the digest covers, returning the best address this build can give for each hit: paragraph id or index and hash for docx, slide id for pptx, sheet and cell for xlsx. On pptx, real slides (in presentation order) are visited before slide layouts, masters and notes masters, so the default page surfaces slide content first. Each match's `text` is a bounded window around the hit, not the whole run — `text_length` and `match_offset` locate it in the full run, and `text_truncated` says whether it was cut; a large result set can also stop early on total response size, reported the same way as `max_results` paging: `truncated=True`. Results come from the session's working copy as opened; `verify` is what reports on the file currently on disk.

NameTypeReqDescription
max_results–––
part–––
querystringyes–
session_idstringyes–
NameTypeReqDescription
baseline_digeststringyesThe canonical digest of this document AS IT WAS WHEN THE SESSION WAS OPENED, and of the working copy these results were read from — not an attestation about the file on disk right now. Call `verify`…
document_may_have_changed_since_openbooleanyesTrue when the document FILE on disk no longer has the size and modification time it had when this session last touched it — so these results may describe a version that no longer exists. It reports w…
matchesarrayyes–
part–yes–
querystringyes–
session_idstringyes–
truncatedbooleanyes–

No examples provided.

insert_paragraph ~261

Insert a new paragraph carrying `text`, BESIDE a paragraph you name, and record it in the session's journal. Pass exactly one anchor — `after_para_id` or `before_para_id`, the `w14:paraId` `find_text` returns. `para_hash` is OPTIONAL and recommended: the paraId already names one specific paragraph, and passing the hash `find_text` reported with it additionally refuses the call if that paragraph's text has moved on since you read it. There is deliberately NO raw index parameter. The new paragraph becomes a SIBLING of the anchor, which keeps it inside the same table cell, textbox or content control. `mode` 'tracked' marks the new paragraph and its run with `w:ins`, so rejecting removes the whole paragraph; 'direct' writes it unmarked and is accounted for by the ledger alone, which the receipt discloses. Seal the session with `commit_document`.

NameTypeReqDescription
after_para_id–––
authorstringyes–
before_para_id–––
modestring––
note–––
para_hash–––
partstringyes–
session_idstringyes–
textstringyes–
NameTypeReqDescription
after–yes–
baseline_digeststringyes–
before–yes–
document_digest_changedbooleanyes–
modestringyes–
note–yes–
opstringyes–
para_id–yes–
para_indexintegeryes–
partstringyes–
partsarrayyes–
result_digeststringyes–
revision_idsarrayyes–
session_idstringyes–

No examples provided.

list_receipts ~51

List every receipt in the store beside a document, flagging the one whose result digest matches the document as it stands now, and naming every file that was skipped and why.

NameTypeReqDescription
documentstringyes–
NameTypeReqDescription
baselinesarrayyes–
caveatstringyes–
documentstringyes–
document_digeststringyes–
receiptsarrayyes–
skippedarrayyes–
storestringyes–

No examples provided.

open_document ~72

Start an editing session: unpack the document to disk, record its baseline digest and part manifest, and sweep expired sessions. Reopening the same unchanged document resumes its live session instead of forking a second one.

NameTypeReqDescription
documentstringyes–
keep_baselineboolean––
ttl_seconds–––
NameTypeReqDescription
baseline_digeststringyes–
baseline_storedbooleanyes–
canonstringyes–
documentstringyes–
expiresstringyes–
kindstringyes–
namestringyes–
partsintegeryes–
resumedbooleanyes–
session_idstringyes–
sweptarrayyes–
swept_skippedarrayyes–

No examples provided.

preview_edits ~111

Report what a batch of edits WOULD do, writing nothing. Runs the same engine against a throwaway copy of the document as it stands on disk right now — including every edit already applied in this session — so a green preview and the apply that follows it cannot disagree. `author` and `mode` are required because the engine's refusals depend on both.

NameTypeReqDescription
authorstringyes–
editsarrayyes–
modestring––
session_idstringyes–
NameTypeReqDescription
caveatstringyes–
outcomesarrayyes–
session_idstringyes–
would_applyintegeryes–

No examples provided.

server_info ~22

Versions, allowed roots, and what this build can and cannot do.

Input schema present but exposes no named parameters.

NameTypeReqDescription
canonstringyes–
caveatstringyes–
editing_availablebooleanyes–
editing_formatsarrayyes–
formatsarrayyes–
read_onlybooleanyes–
receipt_schemastringyes–
rootsarrayyes–
toolstringyes–

No examples provided.

verify ~76

Check a document against its receipt. Reports three distinct outcomes: verified, unknown (no receipt matches this digest) and failed (a receipt matched but a tier failed). Needs no session — the same check runs in CI via `ooxml-ledger verify`.

NameTypeReqDescription
documentstringyes–
original–––
receipt–––
NameTypeReqDescription
baseline_checked–yes–
caveatstringyes–
digeststringyes–
disclosuresarrayyes–
documentstringyes–
exit_codeintegeryes–
outcomestringyes–
reasonsarrayyes–
tiersobjectyes–

No examples provided.

Install

How do I install the io.github.Anselmoo/mcp-ooxml-ledger server?

io.github.Anselmoo/mcp-ooxml-ledger runs locally as a container image, launched with docker run --rm -i ghcr.io/anselmoo/mcp-ooxml-ledger:0.3.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/anselmoo/mcp-ooxml-ledger:0.3.0

# add to Claude Code
claude mcp add anselmoo-mcp-ooxml-ledger -- docker run --rm -i ghcr.io/anselmoo/mcp-ooxml-ledger:0.3.0
Common questions

What is the io.github.Anselmoo/mcp-ooxml-ledger server?

io.github.Anselmoo/mcp-ooxml-ledger is listed in the public MCP registry as io.github.Anselmoo/mcp-ooxml-ledger. Edit Office documents and prove no edit went unrecorded. This page covers its container image (ghcr.io/anselmoo/mcp-ooxml-ledger:0.3.0).

Is the io.github.Anselmoo/mcp-ooxml-ledger server safe to use?

io.github.Anselmoo/mcp-ooxml-ledger scores 50 out of 100 on VerifyMCP. 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 io.github.Anselmoo/mcp-ooxml-ledger server expose?

io.github.Anselmoo/mcp-ooxml-ledger exposes 14 tools: server_info, digest, verify, open_document, close_document, and 9 more. Their descriptions and schemas cost roughly 1,510 tokens of context every time the server is loaded.

Is the io.github.Anselmoo/mcp-ooxml-ledger server still maintained?

io.github.Anselmoo/mcp-ooxml-ledger 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 io.github.Anselmoo/mcp-ooxml-ledger server under?

io.github.Anselmoo/mcp-ooxml-ledger declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.