# io.github.theluckystrike/docx-document-generator-proposal-contract-markdown (remote · mcp.zovo.one)

Create real Word .docx files from your AI chat: proposals, quotes, contracts, statements of work.

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.zovo.one`: 82/100 (this document), [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, [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

- Endpoint: `https://mcp.zovo.one/mcp/docx`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **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 (good).
  - Context-footprint check failed: tool/resource definitions use about 2442 tokens (~152/item across 16 items; 14 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "doc_upload" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 15 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

### How do I install the io.github.theluckystrike/docx-document-generator-proposal-c… MCP server?

io.github.theluckystrike/docx-document-generator-proposal-c… is a hosted endpoint at https://mcp.zovo.one/mcp/docx, so there is nothing to install locally. 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 --transport http theluckystrike-docx-document-generator-proposal- 'https://mcp.zovo.one/mcp/docx'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-docx-document-generator-proposal-": {
      "url": "https://mcp.zovo.one/mcp/docx"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-docx-document-generator-proposal-": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/docx"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-docx-document-generator-proposal-]
url = "https://mcp.zovo.one/mcp/docx"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-docx-document-generator-proposal-": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/docx",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-docx-document-generator-proposal- --url 'https://mcp.zovo.one/mcp/docx' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-docx-document-generator-proposal-:
    url: "https://mcp.zovo.one/mcp/docx"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-docx-document-generator-proposal-": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/docx"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-docx-document-generator-proposal- -t streamable-http -u 'https://mcp.zovo.one/mcp/docx'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-docx-document-generator-proposal-": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/docx"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-20 (score 82, +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-18 (score 81, +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-17 (score 80, 0)

- [functional] Server version: 0.21.0 → 0.22.0

### 2026-09-16 (score 80, +1)

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

### 2026-09-14 (score 79, +1)

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

### 2026-09-11 (score 78, +1)

- [security] Tool “doc_delete_upload” rewrote its description, which is the text the model reads
- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [security] Tool “doc_from_markdown” rewrote its description, which is the text the model reads
- [functional] New prompt “upgrade_to_pro”
- [functional] New resource “pricing”

### 2026-09-10 (score 77, +1)

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

### 2026-09-09 (score 76, 0)

- [security] Tool “doc_fill_template” rewrote its description, which is the text the model reads
- [security] Tool “business_set” rewrote its description, which is the text the model reads
- [security] Tool “doc_from_markdown” rewrote its description, which is the text the model reads
- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [security] Tool “license_status” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “license_activate” reworded the description of “key”

## MCP tools (14)

### `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` (~110 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:

- `docx_base64` (string): The .docx itself, base64-encoded, instead of uploading it first
- `format` (string): text (default) returns the readable text, json returns the block structure in document order
- `path` (string): Name of a document uploaded with doc_upload

### `doc_to_html` (~122 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): Name for the downloaded .html file
- `overwrite` (boolean): Replace out_path if a file is already there. Default false: an existing file is never overwritten
- `path` (string, required): Name of a document uploaded with doc_upload, or a document this server just wrote

### `doc_fill_template` (~183 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:

- `docx_base64` (string): The .docx template itself, base64-encoded, instead of uploading it first
- `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): Name of a template uploaded with doc_upload
- `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` (~55 tokens)

License status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

### `license_activate` (~76 tokens)

Activate license

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

### `doc_upload` (~302 tokens)

Upload a .docx to work on

Send an existing Word document to this hosted endpoint. There is no filesystem here, so instead of a path you upload the file once with doc_upload and then pass its name as `path` to doc_read, doc_to_html and doc_fill_template. Give exactly one of docx_base64 or url. url: fetch a public file instead of pasting base64 (recommended above about 10 KB): a 13 KB base64 paste can take minutes to write out, while a url costs one line and the fetch happens here (10 second timeout, at most 3 redirects, public http(s) hosts only, 2 MB cap). Uploads are kept for your token between calls; doc_read and doc_fill_template also take docx_base64 directly; that file is stored under the name you give (default 'inline' / 'template') and can be removed with doc_delete_upload. Documents this server writes come back as a download link valid for one hour.

Input parameters:

- `docx_base64` (string): The .docx file, base64-encoded
- `name` (string, required): Name to refer to this document by: 1-64 characters of letters, digits, underscore or dash, e.g. "contract"
- `url` (string): url: fetch a public file instead of pasting base64 (recommended above about 10 KB). Public http(s) only; private, link-local and this endpoint's own zone are refused

### `doc_files` (~20 tokens)

List uploaded documents

List the documents uploaded for your token, with their sizes.

### `doc_delete_upload` (~56 tokens)

Delete an uploaded document

Delete one document uploaded for your token: name is the name it was uploaded under, without .docx. doc_files lists them. A name nothing is stored under is refused and nothing is deleted.

Input parameters:

- `name` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-docx-document-generator-proposal-contract-markdown/mcp-docx#diagnostics

## Score history

- 2026-09-20: 82
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 78
- 2026-09-10: 77
- 2026-09-09: 76
- 2026-09-08: 76
- 2026-09-07: 36
- 2026-09-06: 36
- 2026-09-05: 36
- 2026-09-04: 36
- 2026-09-03: 36

## Common questions

### What is the io.github.theluckystrike/docx-document-generator-proposal-c… MCP server?

io.github.theluckystrike/docx-document-generator-proposal-c… is an MCP server listed in the public MCP registry as io.github.theluckystrike/docx-document-generator-proposal-c…. Create real Word .docx files from your AI chat: proposals, quotes, contracts, statements of work. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/docx).

### Is the io.github.theluckystrike/docx-document-generator-proposal-c… MCP server safe to use?

io.github.theluckystrike/docx-document-generator-proposal-c… scores 82 out of 100 on VerifyMCP. 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/docx-document-generator-proposal-c… MCP server expose?

io.github.theluckystrike/docx-document-generator-proposal-c… exposes 14 tools: business_set, doc_create, doc_from_markdown, doc_read, doc_to_html, and 9 more. Their descriptions and schemas cost roughly 2,365 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/docx-document-generator-proposal-c… MCP server require authentication?

Yes. io.github.theluckystrike/docx-document-generator-proposal-c… asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.theluckystrike/docx-document-generator-proposal-c… MCP server still maintained?

io.github.theluckystrike/docx-document-generator-proposal-c… 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.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/docx
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/docx
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/docx
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-docx-document-generator-proposal-contract-markdown/mcp-docx.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-docx-document-generator-proposal-contract-markdown/mcp-docx.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-docx-document-generator-proposal-contract-markdown/mcp-docx