# io.github.theluckystrike/docx-document-generator-proposal-contract-markdown (mcpb · docx.mcpb) Create real Word .docx files from your AI chat: proposals, quotes, contracts, statements of work. - Trust score: 48/100 (low) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-09-20 ## Components - remote · `mcp.zovo.one`: 82/100, [markdown](https://verifymcp.io/servers/theluckystrike-docx-document-generator-proposal-contract-markdown/mcp-docx.md), [page](https://verifymcp.io/servers/theluckystrike-docx-document-generator-proposal-contract-markdown/mcp-docx) - mcpb · `docx.mcpb`: 48/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-docx-document-generator-proposal-contract-markdown/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-docx-mcpb.md), [page](https://verifymcp.io/servers/theluckystrike-docx-document-generator-proposal-contract-markdown/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-docx-mcpb) ## Channel facts - Registry: `mcpb` - Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/docx.mcpb` - Version: `0.22.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-09-20. - **Supply Chain Security**: 23/100 - Malware scan not yet available for this package. - Known CVEs were checked across the 117 of 117 dependencies we could resolve, so this covers what we could see, not the whole tree. - No install/post-install scripts declared. - 44 of 117 dependencies flagged as unhealthy. - **Provenance & Transparency**: 45/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - Clear OSI-approved license (MIT). - Actively maintained (last published 2 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 79/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 2049 tokens (~170/item across 12 items; 11 tools + 1 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**: 95/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 84% 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 12 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 - Download bundle: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/docx.mcpb` ## 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-09-17 (score 48) First indexed and scored. ## MCP tools (11) ### `business_set` (~399 tokens) Set your business details Store the sender details printed on every proposal, contract and letter, plus the currency, VAT, terms and prefix defaults. It writes the SAME shared profile as the invoice server's business_set. Input parameters: - `address` (string): Postal address, newlines allowed - `bank` (string): Bank name / BIC - `brand_color` (string): Letterhead colour as a hex code, e.g. 1F3864 (Pro) - `default_currency` (string): ISO code, e.g. EUR, USD. Default EUR - `default_tax_rate` (number): Default VAT percent, quoted on proposals - `email` (string): Your own email address, printed on every letterhead. Leave it out unless the user gave it: a document that shows an address nobody supplied is worse than one that shows [add: email] - `iban` (string): IBAN or account number for payment - `invoice_prefix` (string): Reference prefix used by mcp-invoice; this profile has the same field shape as mcp-invoice, so one profile serves both - `logo_path` (string): Path to a PNG or JPG logo for the letterhead (Pro) - `name` (string, required): Your business or freelancer name, printed on the letterhead of every proposal, contract and letter - `payment_terms_days` (number): Default days until payment is due. Default 14 - `phone` (string): Your own phone number. Same rule as email: only if the user gave it - `tax_rate` (number): Alias for default_tax_rate - `timezone` (string): IANA zone you work in, e.g. Europe/Warsaw. Shared with time-tracker and timezone as your home zone - `vat` (number): Alias for default_tax_rate - `vat_id` (string): VAT / tax registration id - `vat_rate` (number): Alias for default_tax_rate ### `doc_create` (~213 tokens) Create a Word document Call this tool to write a real .docx file from structured sections. Returns the file path, the number of blocks written and the layout used. Free and unlimited. Input parameters: - `date` (string): Date line for the letter layout, default today - `out_path` (string): Where to write the .docx. Defaults to the data directory - `overwrite` (boolean): Replace out_path if a file is already there. Default false: an existing file is never overwritten - `recipient` (string): Addressee block for the letter layout - `sections` (array, required): Sections in order. Each one may carry a heading, paragraphs, a bullet or numbered list and a table - `style` (string): Layout, default plain. plain is the title and the body; letter adds a sender block top right, a date and the addressee; proposal adds a letterhead band and a cover title - `title` (string, required): Document title, used as the top heading and the file name ### `doc_from_markdown` (~182 tokens) Markdown to Word Call this tool to turn markdown into a .docx, returning the file and a count of blocks by type. Headings, lists, GFM tables and code fences are honoured. Empty markdown is refused, and so is overwriting without the flag. Input parameters: - `markdown` (string, required): The markdown source. ATX headings, paragraphs, bullet and numbered lists, GFM pipe tables and fenced code blocks as monospace are honoured, as are **bold**, *italic* and `code` inline - `out_path` (string): Where to write the .docx. Defaults to the data directory - `overwrite` (boolean): Replace out_path if a file is already there. Default false: an existing file is never overwritten - `style` (string) - `title` (string): Document title; defaults to the first heading in the markdown ### `doc_read` (~119 tokens) Read a Word document Call this tool to extract the text of an existing .docx. Returns an outline of the headings and the full text in document order, or the block structure. Free and unlimited. Input parameters: - `format` (string): text (default) returns the readable text, json returns the block structure: headings with their levels, paragraphs, list items and tables, in document order - `path` (string, required): Path to the .docx file. Files produced by Word, Google Docs or this server all work; legacy .doc and .rtf do not ### `doc_to_html` (~138 tokens) Word document to HTML Call this tool to convert a .docx to semantic HTML you can open in a browser and print to PDF. Returns the path of the .html file. This is the supported PDF route; no PDF is rendered here. Free and unlimited. Input parameters: - `out_path` (string): Where to write the .html. Defaults next to the source file. Open the result and print it to PDF; direct PDF output is not offered here - `overwrite` (boolean): Replace out_path if a file is already there. Default false: an existing file is never overwritten - `path` (string, required): Path to the .docx file to convert ### `doc_fill_template` (~200 tokens) Fill a Word template Call this tool to replace {{placeholders}} in a .docx and write a new file, reporting what was filled, unfilled or ignored. Call it with no values to list them. Free: templates up to 10 placeholders. Input parameters: - `out_path` (string): Where to write the filled .docx. Defaults to