McpStamp Word Documents
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS
Create Word .docx files from sections or markdown, fill templates, and read text from a .docx.
Available components
Last scanned (18 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Documents and Files
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. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2559 tokens (~159/item across 16 items; 14 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 84% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 16 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
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.
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 2 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “doc_upload” is now declared destructive security
- Tool “doc_delete_upload” is now declared destructive security
- Destructive annotations: All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- 16 Oct 26 0
- Server version: 0.22.0 → 0.22.6 functional
- 10 Oct 26 +1
- Stability: 0.93 → pass security
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 93. That category is still filling its 30-day observation window: 26 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.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 4 Nov 2026 · Probed https://mcp.zovo.one/mcp/docx
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 39e1adfa4eb6500e0e3d48868766e3e9 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/docx"
Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/docx"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/docx |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.zovo.one/mcp/docx |
| Authorisation server | https://mcp.zovo.one |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/docx | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/docx | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/docx |
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 →
business_set Set your business details ~399
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| 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 | yes | 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 |
No output schema declared.
No examples provided.
contract_create Create a service agreement ~229
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.
| Name | Type | Req | Description |
|---|---|---|---|
| clauses | array | – | Extra clauses to append, one paragraph each |
| client | string | yes | The client's legal name |
| end_date | string | – | YYYY-MM-DD, omit for an open-ended engagement |
| fee | object | yes | – |
| 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 | yes | 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 | yes | YYYY-MM-DD |
No output schema declared.
No examples provided.
doc_create Create a Word document ~213
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Document title, used as the top heading and the file name |
No output schema declared.
No examples provided.
doc_delete_upload Delete an uploaded document ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
doc_files List uploaded documents ~20
List the documents uploaded for your token, with their sizes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
doc_fill_template Fill a Word template ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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"} |
No output schema declared.
No examples provided.
doc_from_markdown Markdown to Word ~182
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.
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | 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 |
No output schema declared.
No examples provided.
doc_read Read a Word document ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
doc_to_html Word document to HTML ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Name of a document uploaded with doc_upload, or a document this server just wrote |
No output schema declared.
No examples provided.
doc_upload Upload a .docx to work on ~302
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.
| Name | Type | Req | Description |
|---|---|---|---|
| docx_base64 | string | – | The .docx file, base64-encoded |
| name | string | yes | 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 |
No output schema declared.
No examples provided.
license_activate Activate license ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
proposal_create Create a proposal ~269
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | 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 | yes | – |
| project_title | string | yes | 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 |
No output schema declared.
No examples provided.
proposal_update Update a proposal ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | – |
| deliverables | array | – | – |
| price | object | – | – |
| project_title | string | – | – |
| reference | string | yes | 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 | – | – |
No output schema declared.
No examples provided.
How do I install the McpStamp Word Documents MCP server?
McpStamp Word Documents 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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-docx-document-generator-proposal- 'https://mcp.zovo.one/mcp/docx'
What is the McpStamp Word Documents MCP server?
McpStamp Word Documents is an MCP server listed in the public MCP registry as io.github.theluckystrike/docx-document-generator-proposal-c…. Create Word .docx files from sections or markdown, fill templates, and read text from a .docx. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/docx).
Is the McpStamp Word Documents MCP server safe to use?
McpStamp Word Documents scores 93 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 McpStamp Word Documents MCP server expose?
McpStamp Word Documents 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 McpStamp Word Documents MCP server require authentication?
Yes. McpStamp Word Documents 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 McpStamp Word Documents MCP server still maintained?
McpStamp Word Documents is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.