io.github.mdfifty50-boop/docx-forge
NPM · DOCX-FORGE-MCP · SCANNED SEP 20
Professional document generation from structured data
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
- 52 of 130 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 148 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability48
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 833 tokens (~83/item across 10 items; 9 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "merge_documents" implies "merge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 10 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 io.github.mdfifty50-boop/docx-forge MCP server?
io.github.mdfifty50-boop/docx-forge runs locally as an npm package, launched with npx -y docx-forge-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · docx-forge-mcp
claude mcp add mdfifty50-boop-docx-forge -- npx -y docx-forge-mcp
{
"mcpServers": {
"mdfifty50-boop-docx-forge": {
"command": "npx",
"args": [
"-y",
"docx-forge-mcp"
]
}
}
} {
"servers": {
"mdfifty50-boop-docx-forge": {
"command": "npx",
"args": [
"-y",
"docx-forge-mcp"
]
}
}
} codex mcp add mdfifty50-boop-docx-forge -- npx -y docx-forge-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mdfifty50-boop-docx-forge": {
"type": "local",
"command": [
"npx",
"-y",
"docx-forge-mcp"
],
"enabled": true
}
}
} openclaw mcp add mdfifty50-boop-docx-forge --command npx --arg -y --arg docx-forge-mcp
mcp_servers:
mdfifty50-boop-docx-forge:
command: "npx"
args: ["-y", "docx-forge-mcp"] {
"McpServers": {
"mdfifty50-boop-docx-forge": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"docx-forge-mcp"
]
}
}
} assistant mcp add mdfifty50-boop-docx-forge -t stdio -c npx -a -y docx-forge-mcp
{
"mcpServers": {
"mdfifty50-boop-docx-forge": {
"command": "npx",
"args": [
"-y",
"docx-forge-mcp"
]
}
}
} 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.
- 19 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.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 12 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.
- 10 Sept 26 −2
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed npm/docx-forge-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 130 packages
| Packages resolved | 130 |
|---|---|
| Stale | 52 |
| 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 →
add_section ~108
Append a new section (heading + body content) to the end of an existing .docx document. The document is updated in place.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Section body content (markdown supported) |
| filePath | string | yes | Path to the existing .docx file |
| heading | string | yes | Section heading text |
| headingLevel | integer | – | Heading level: 1 = H1 (largest) through 6 = H6 (smallest). Default: 2 |
No output schema declared.
No examples provided.
add_table ~126
Insert a formatted table into an existing .docx document. The table is appended at the end of the document with bold header row and standard cell borders.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Path to the existing .docx file |
| headers | array | yes | Column header labels (e.g., ["Name", "Role", "Department"]) |
| rows | array | yes | 2D array of table data. Each inner array is one row and must match the number of headers. Example: [["Alice", "Engineer", "Tech"], ["Bob", "Designer", "UX"]] |
No output schema declared.
No examples provided.
create_document ~160
Create a new .docx Word document from markdown or plain text content. Supports headings (#, ##, ###), bold (**text**), italic (*text*), bullet lists (- item), numbered lists (1. item), and blank lines between paragraphs.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | Author name stored in document metadata |
| content | string | yes | Document body content as markdown. Supports headings (#, ##, ###), bold (**text**), italic (*text*), bullet lists (- item), and numbered lists (1. item). |
| outputPath | string | yes | Absolute or relative path where the .docx file will be saved (e.g., /tmp/report.docx) |
| title | string | yes | Document title — appears as the document heading |
No output schema declared.
No examples provided.
export_to_pdf ~86
Convert a .docx file to PDF. Attempts conversion via LibreOffice (best fidelity) then pandoc. Returns success status and the method used. Requires LibreOffice or pandoc to be installed on the system.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Path to the source .docx file |
| outputPath | string | yes | Path where the output .pdf file will be saved |
No output schema declared.
No examples provided.
get_document_stats ~63
Get statistics for a .docx document: word count, character count, estimated page count (at 250 words/page), number of sections (headings), and number of tables.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Path to the .docx file to analyze |
No output schema declared.
No examples provided.
health_check ~20
Returns server health, uptime, version, and call stats
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
merge_documents ~92
Combine multiple .docx files into a single document. Each source document is separated by a horizontal divider. Useful for assembling reports, consolidating contracts, or combining chapter files.
| Name | Type | Req | Description |
|---|---|---|---|
| filePaths | array | yes | Array of paths to .docx files to merge (minimum 2). Files are merged in the order given. |
| outputPath | string | yes | Path where the merged .docx file will be saved |
No output schema declared.
No examples provided.
read_document ~55
Extract all text, paragraph list, headings, and file metadata from an existing .docx file. Returns structured data suitable for further processing or display.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Path to the .docx file to read |
No output schema declared.
No examples provided.
replace_text ~118
Find and replace text in an existing .docx document. Useful for template substitution — e.g., replacing {{CLIENT_NAME}} with an actual name, or updating dates and contract values.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Path to the .docx file to modify |
| find | string | yes | Text string to search for |
| replace | string | yes | Replacement text (can be empty string to delete the found text) |
| replaceAll | boolean | – | If true (default), replace every occurrence. If false, replace only the first occurrence. |
No output schema declared.
No examples provided.
What is the io.github.mdfifty50-boop/docx-forge MCP server?
io.github.mdfifty50-boop/docx-forge is an MCP server listed in the public MCP registry as io.github.mdfifty50-boop/docx-forge. Professional document generation from structured data. This page covers its npm package (docx-forge-mcp).
Is the io.github.mdfifty50-boop/docx-forge MCP server safe to use?
io.github.mdfifty50-boop/docx-forge scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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.mdfifty50-boop/docx-forge MCP server expose?
io.github.mdfifty50-boop/docx-forge exposes 9 tools: health_check, create_document, read_document, add_section, replace_text, and 4 more. Their descriptions and schemas cost roughly 828 tokens of context every time the server is loaded.
Is the io.github.mdfifty50-boop/docx-forge MCP server still maintained?
io.github.mdfifty50-boop/docx-forge is still listed as active in the MCP registry. We last reached this channel on 20 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 io.github.mdfifty50-boop/docx-forge MCP server under?
io.github.mdfifty50-boop/docx-forge declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.