ooxml-integrity
PYPI · OOXML-INTEGRITY
Checks .docx and .pptx files after automated editing for lost comments, tracked changes and notes.
Available components
Last scanned (18 hours ago)
Scores higher than 57% of PyPI servers
Category Documents and Files
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Dmitry-Kov/ooxml-integrity). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 556 tokens (~278/item across 2 items; 2 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
Checks we ran (14)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
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 →
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 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 19 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 16 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 10 Nov 26 65
First indexed and scored.
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 Nov 2026 · Analysed pypi/ooxml-integrity@0.10.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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Dmitry-Kov/ooxml-integrity |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Dmitry-Kov/ooxml-integrity/.github/workflows/release.yml@refs/tags/v0.10.0 |
| Rekor log index | 3782594547 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:af54e4c96bddcfff07364d5889c80ff05fc5d9b92c76a5ae615ad42f9a391976 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| 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 →
check Check a .docx or .pptx ~141
Self-check one .docx or .pptx: comment anchors, footnotes, styles, numbering, relationships and tracked-change markup in a document; text that overflows its box and shapes off the slide in a deck. Same as `ooxml-integrity check PATH --json --coverage`. Without the original it cannot see what an edit removed, such as a deleted comment: use compare when the original is available. Returns a one-line verdict, then the JSON report; exit_code 1 means findings at or above fail-on.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | path on this machine; absolute, or relative to the server's working directory. URLs are rejected |
No output schema declared.
No examples provided.
compare Check an edited .docx against its original ~282
Everything check does on the edited file, plus what the edit lost relative to the original: comments, tracked insertions and deletions, footnotes and endnotes, headers and footers, text. Same as `ooxml-integrity check EDITED --against SOURCE --json --coverage`. For a .pptx only the layout checks run and the comparison is reported as not performed (FID000). If the user asked for a change that removes something, such as accepting or rejecting a tracked change or rewriting a header untracked, declare it in expect: a matching finding is reported as expected instead of failing, and an expectation nothing matches fails with EXP001.
| Name | Type | Req | Description |
|---|---|---|---|
| edited | string | yes | the edited copy; path on this machine; absolute, or relative to the server's working directory. URLs are rejected |
| expect | array | – | changes the edit was asked to make, as [[expect]] entries in docs/configuration.md, without path |
| introduced | boolean | – | true reports only what the edit introduced: a finding the original already has, such as a comment an earlier tool orphaned, is listed as suppressed instead of failing. Lost content (FID) and anything… |
| source | string | yes | the original document; path on this machine; absolute, or relative to the server's working directory. URLs are rejected |
No output schema declared.
No examples provided.
How do I install the ooxml-integrity MCP server?
ooxml-integrity runs locally as a PyPI package, launched with uvx ooxml-integrity mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · ooxml-integrity
claude mcp add dmitry-kov-ooxml-integrity -- uvx ooxml-integrity mcp
What is the ooxml-integrity MCP server?
ooxml-integrity is an MCP server listed in the public MCP registry as io.github.Dmitry-Kov/ooxml-integrity. Checks .docx and .pptx files after automated editing for lost comments, tracked changes and notes. This page covers its PyPI package (ooxml-integrity).
Is the ooxml-integrity MCP server safe to use?
ooxml-integrity scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 ooxml-integrity MCP server expose?
ooxml-integrity exposes 2 tools: check, compare. Their descriptions and schemas cost roughly 423 tokens of context every time the server is loaded.
Is the ooxml-integrity MCP server still maintained?
ooxml-integrity is still listed as active in the MCP registry. We last reached this channel on 21 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 ooxml-integrity MCP server under?
ooxml-integrity declares the MIT 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 ooxml-integrity MCP server?
VerifyMCP ran 14 checks on ooxml-integrity, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about ooxml-integrity: Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.