io.github.theluckystrike/letterhead
MCPB · DOCX.MCPB · SCANNED SEP 20
Print your business letterhead on Word docs, proposals and contracts from chat.
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 Security23
- Malware scan not yet available for this package.Unverified
- Known CVEs were checked across the 117 of 117 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 44 of 117 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 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 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
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
mcpb · docx.mcpb
Download bundleEvery 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 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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 14 Sept 26 +3
- Stability: unverified → 0.23 ▲ functional
- 7 Sept 26 48
First indexed and scored.
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 mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/docx.mcpb@0.21.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
Background: How many MCP packages publish verified provenance →
Dependencies 117 packages
| Packages resolved | 117 |
|---|---|
| Stale | 44 |
| 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 →
business_set Set your business details ~400
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.
| 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_fill_template Fill a Word template ~199
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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"} |
No output schema declared.
No examples provided.
doc_from_markdown Markdown to Word ~162
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.
| 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 ~119
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 |
|---|---|---|---|
| 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 | yes | Path to the .docx file. Files produced by Word, Google Docs or this server all work; legacy .doc and .rtf do not |
No output schema declared.
No examples provided.
doc_to_html Word document to HTML ~138
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 | – | 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 | yes | Path to the .docx file to convert |
No output schema declared.
No examples provided.
license_activate Activate license ~42
Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~23
Show whether this server runs in free or Pro mode and where to upgrade.
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.
What is the io.github.theluckystrike/letterhead MCP server?
io.github.theluckystrike/letterhead is an MCP server listed in the public MCP registry as io.github.theluckystrike/letterhead. Print your business letterhead on Word docs, proposals and contracts from chat. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/docx.mcpb).
Is the io.github.theluckystrike/letterhead MCP server safe to use?
io.github.theluckystrike/letterhead 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/letterhead MCP server expose?
io.github.theluckystrike/letterhead 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/letterhead MCP server under?
io.github.theluckystrike/letterhead declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.