# ooxml-integrity (pypi · ooxml-integrity)

Checks .docx and .pptx files after automated editing for lost comments, tracked changes and notes.

- Trust score: 65/100 (medium)
- Change this week: −15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- pypi · `ooxml-integrity`: 65/100 (this document), [markdown](https://verifymcp.io/servers/dmitry-kov-ooxml-integrity/ooxml-integrity.md), [page](https://verifymcp.io/servers/dmitry-kov-ooxml-integrity/ooxml-integrity)

## Channel facts

- Registry: `pypi`
- Package: `ooxml-integrity`
- Version: `0.10.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 0 of 3 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Dmitry-Kov/ooxml-integrity).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

## Install

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

### Claude

```bash
claude mcp add dmitry-kov-ooxml-integrity -- uvx ooxml-integrity mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dmitry-kov-ooxml-integrity": {
      "command": "uvx",
      "args": [
        "ooxml-integrity",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dmitry-kov-ooxml-integrity": {
      "command": "uvx",
      "args": [
        "ooxml-integrity",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dmitry-kov-ooxml-integrity -- uvx ooxml-integrity mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dmitry-kov-ooxml-integrity": {
      "type": "local",
      "command": [
        "uvx",
        "ooxml-integrity",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dmitry-kov-ooxml-integrity --command uvx --arg ooxml-integrity --arg mcp
```

### Hermes

```yaml
mcp_servers:
  dmitry-kov-ooxml-integrity:
    command: "uvx"
    args: ["ooxml-integrity", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dmitry-kov-ooxml-integrity": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "ooxml-integrity",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dmitry-kov-ooxml-integrity -t stdio -c uvx -a ooxml-integrity mcp
```

### Other

```json
{
  "mcpServers": {
    "dmitry-kov-ooxml-integrity": {
      "command": "uvx",
      "args": [
        "ooxml-integrity",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 65, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-19 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-18 (score 65, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-16 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-15 (score 65, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-12 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-10 (score 65)

First indexed and scored.

## MCP tools (2)

### `check` (~141 tokens)

Check a .docx or .pptx

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.

Input parameters:

- `path` (string, required): path on this machine; absolute, or relative to the server's working directory. URLs are rejected

### `compare` (~282 tokens)

Check an edited .docx against its original

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.

Input parameters:

- `edited` (string, required): 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, required): the original document; path on this machine; absolute, or relative to the server's working directory. URLs are rejected

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/dmitry-kov-ooxml-integrity/ooxml-integrity#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 80
- 2026-11-19: 80
- 2026-11-18: 65
- 2026-11-17: 80
- 2026-11-16: 80
- 2026-11-15: 65
- 2026-11-14: 80
- 2026-11-13: 80
- 2026-11-12: 80
- 2026-11-11: 65
- 2026-11-10: 65

## Common questions

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

## Links

- PyPI project: https://pypi.org/project/ooxml-integrity/
- Socket report: https://socket.dev/pypi/package/ooxml-integrity
- Repository: https://github.com/Dmitry-Kov/ooxml-integrity
- Website: https://github.com/Dmitry-Kov/ooxml-integrity/blob/main/docs/mcp.md
- Changelog RSS feed: https://verifymcp.io/servers/dmitry-kov-ooxml-integrity/ooxml-integrity.xml
- Changelog JSON feed: https://verifymcp.io/servers/dmitry-kov-ooxml-integrity/ooxml-integrity/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dmitry-kov-ooxml-integrity/ooxml-integrity.json
- HTML version of this page: https://verifymcp.io/servers/dmitry-kov-ooxml-integrity/ooxml-integrity
