# io.github.theluckystrike/templates (mcpb · docx.mcpb)

Reusable docx templates: placeholders for proposals, contracts, quotes, SOWs.

- Trust score: 54/100 (low)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- mcpb · `docx.mcpb`: 54/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-templates/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-docx-mcpb.md), [page](https://verifymcp.io/servers/theluckystrike-templates/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-docx-mcpb)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/docx.mcpb`
- Version: `0.21.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 13 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/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 1969 tokens (~164/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**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.

## Install

- Download bundle: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.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-19 (score 54, +1)

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

### 2026-09-17 (score 53, +1)

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

### 2026-09-15 (score 52, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-07 (score 48)

First indexed and scored.

## MCP tools (11)

### `business_set` (~400 tokens)

Set your business details

The sender profile printed on every proposal, contract and letter. The SAME profile invoice's business_set writes: it goes to the shared profile, so it also sets your invoice issuer and default VAT.

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` (~162 tokens)

Markdown to Word

Call this tool to turn markdown into a .docx. Returns the file path and a count of the blocks written, by type. Free and unlimited.

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` (~199 tokens)

Fill a Word template

Call this tool to replace {{placeholders}} in an existing .docx and write a new file. Returns the new path and which placeholders were replaced, unfilled or ignored. Call with no values to list a template's placeholders.

Input parameters:

- `out_path` (string): Where to write the filled .docx. Defaults to <template>-filled.docx
- `overwrite` (boolean): Replace out_path if a file is already there. Default false: an existing file is never overwritten
- `template_path` (string, required): Path to the .docx template containing {{placeholders}}. Every style, table, header, footer and image of the original is kept. Placeholders split across runs by Word's editor are handled, because the…
- `values` (object): Placeholder name to value, e.g. {client: "Acme", fee: "EUR 4,500.00"}

### `proposal_create` (~269 tokens)

Create a proposal

Call this tool to produce a client-ready .docx proposal from summary, scope, deliverables, timeline, price and terms. Returns the reference, the total and the file path. Free tier: 3 proposals or contracts per month.

Input parameters:

- `client` (string, required): Client name, printed as 'Prepared for'. The letterhead comes from your business_set profile
- `deliverables` (array): What the client receives, one bullet each. Omitted from the document if not given or empty
- `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
- `price` (object, required)
- `project_title` (string, required): Project title
- `scope` (array): What is in scope, one bullet each. Omitted from the document if not given or empty
- `summary` (string): One or two paragraphs on the problem and the approach. Omitted from the document if not given
- `timeline` (array): Phases and their durations, rendered as a table. Omitted from the document if not given or empty
- `valid_until` (string): YYYY-MM-DD, the date the quote expires

### `proposal_update` (~149 tokens)

Update a proposal

Rewrite an existing proposal in place from its reference. Only the fields you pass change; the rest comes from the data stored at creation. Returns the fields that changed and the file path.

Input parameters:

- `client` (string)
- `deliverables` (array)
- `price` (object)
- `project_title` (string)
- `reference` (string, required): The proposal reference, e.g. PROP-2026-0001. The same file and the same reference number are kept, so no second document is burned against the free-tier monthly count
- `scope` (array)
- `summary` (string)
- `timeline` (array)
- `valid_until` (string)

### `contract_create` (~229 tokens)

Create a service agreement

Call this tool to produce a freelance service agreement .docx. Returns the reference, the fee and the file path. It is a template skeleton for a lawyer to review, not legal advice. Free tier: 3 agreements per month.

Input parameters:

- `clauses` (array): Extra clauses to append, one paragraph each
- `client` (string, required): The client's legal name
- `end_date` (string): YYYY-MM-DD, omit for an open-ended engagement
- `fee` (object, required)
- `governing_law` (string): e.g. 'the laws of Poland'
- `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
- `services` (string, required): What you will do, one or two sentences. The document adds parties, term, fee and schedule, plus standard clauses on intellectual property, confidentiality, independent contractor status, liability, t…
- `start_date` (string, required): YYYY-MM-DD

### `license_status` (~23 tokens)

License status

Show whether this server runs in free or Pro mode and where to upgrade.

### `license_activate` (~42 tokens)

Activate license

Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.

Input parameters:

- `key` (string, required): License key from the checkout confirmation page

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/theluckystrike-templates/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-docx-mcpb#diagnostics

## Score history

- 2026-09-20: 54
- 2026-09-19: 54
- 2026-09-18: 53
- 2026-09-17: 53
- 2026-09-16: 52
- 2026-09-15: 52
- 2026-09-14: 48
- 2026-09-13: 48
- 2026-09-12: 48
- 2026-09-11: 48
- 2026-09-10: 48
- 2026-09-09: 48
- 2026-09-08: 48
- 2026-09-07: 48

## Common questions

### What is the io.github.theluckystrike/templates MCP server?

io.github.theluckystrike/templates is an MCP server listed in the public MCP registry as io.github.theluckystrike/templates. Reusable docx templates: placeholders for proposals, contracts, quotes, SOWs. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/docx.mcpb).

### Is the io.github.theluckystrike/templates MCP server safe to use?

io.github.theluckystrike/templates scores 54 out of 100 on VerifyMCP. 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.theluckystrike/templates MCP server expose?

io.github.theluckystrike/templates exposes 11 tools: business_set, doc_create, doc_from_markdown, doc_read, doc_to_html, and 6 more. Their descriptions and schemas cost roughly 1,943 tokens of context every time the server is loaded.

### What licence is the io.github.theluckystrike/templates MCP server under?

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

## Links

- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/docx
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-templates/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-docx-mcpb.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-templates/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-docx-mcpb.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-templates/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-docx-mcpb
