io.github.theluckystrike/resume-cover-letter-docx-generator
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
Tailor a resume and write a cover letter as real Word .docx files from facts you stored once.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 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 1972 tokens (~131/item across 15 items; 13 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 Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 65% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 14 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
How do I install the io.github.theluckystrike/resume-cover-letter-docx-generator MCP server?
io.github.theluckystrike/resume-cover-letter-docx-generator is a hosted endpoint at https://mcp.zovo.one/mcp/resume, 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-resume-cover-letter-docx-generato 'https://mcp.zovo.one/mcp/resume'
{
"mcpServers": {
"theluckystrike-resume-cover-letter-docx-generato": {
"url": "https://mcp.zovo.one/mcp/resume"
}
}
} {
"servers": {
"theluckystrike-resume-cover-letter-docx-generato": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/resume"
}
}
} [mcp_servers.theluckystrike-resume-cover-letter-docx-generato] url = "https://mcp.zovo.one/mcp/resume"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-resume-cover-letter-docx-generato": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/resume",
"enabled": true
}
}
} openclaw mcp add theluckystrike-resume-cover-letter-docx-generato --url 'https://mcp.zovo.one/mcp/resume' --transport streamable-http
mcp_servers:
theluckystrike-resume-cover-letter-docx-generato:
url: "https://mcp.zovo.one/mcp/resume" {
"McpServers": {
"theluckystrike-resume-cover-letter-docx-generato": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/resume"
}
}
} assistant mcp add theluckystrike-resume-cover-letter-docx-generato -t streamable-http -u 'https://mcp.zovo.one/mcp/resume'
{
"mcpServers": {
"theluckystrike-resume-cover-letter-docx-generato": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/resume"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +55
- Authorization: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.30 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Server version: 0.21.0 → 0.22.0 functional
- 17 Sept 26 −54
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.23 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 15 Sept 26 +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.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
- Tool “resume_to_html” rewrote its description, which is the text the model reads 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
- New prompt “upgrade_to_pro” functional
- New resource “pricing” functional
- 10 Sept 26 +1
- Tool “resume_read” rewrote its description, which is the text the model reads security
- Tool “resume_to_html” rewrote its description, which is the text the model reads security
- Tool “resume_to_markdown” rewrote its description, which is the text the model reads security
- Tool “cover_letter_create” 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 security
- Tool “profile_get” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “license_activate” reworded the description of “key” cosmetic
- 9 Sept 26 +39
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: 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. security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 65 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: good 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 20 Sept 2026 · Probed https://mcp.zovo.one/mcp/resume
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 | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| 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 Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
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/resume | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/resume | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/resume |
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 →
cover_letter_create Write a cover letter .docx ~228
Call this tool to write a one-page cover letter .docx from the stored profile and return the path, word count and bracketed prompts. Nothing from the posting is restated as yours. Free: 3 a month.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
| highlights | array | – | Points to lead with. Each is checked against the profile; anything not found there is returned as a bracketed prompt, not printed as fact. |
| hiring_manager | string | – | – |
| job_description | string | – | Paste the posting. Used only to pick which of your own skills to lead with; no figure from the posting is ever restated as yours. |
| out_path | string | – | Where to write the .docx. Defaults to <data dir>/documents/<company>-<role>-cover-letter.docx, numbered -2, -3, ... if that exists. |
| overwrite | boolean | – | Replace an existing file at out_path. Default false: the call fails and nothing is written. |
| role | string | yes | – |
| tone | string | – | Default "formal". |
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_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.
profile_get Show the stored profile ~52
Return the stored CV profile exactly as resume_create, cover_letter_create and tailor_to_job will use it, plus the variant read and every stored variant name. Call it before any rewrite.
| Name | Type | Req | Description |
|---|---|---|---|
| variant | string | – | – |
No output schema declared.
No examples provided.
profile_set Store your CV facts ~414
Store the profile every resume and cover letter is built from: contact details, summary, skills, roles with bullets, education, certifications and languages. Returns a count of what was stored.
| Name | Type | Req | Description |
|---|---|---|---|
| accent_color | string | – | Letterhead colour, six hex digits, e.g. 1F3864. Pro only. |
| certifications | array | – | – |
| education | array | – | – |
| string | – | Your own email address. Leave it out and the shared business profile's email is used; with neither, letters and letterheads show "[add: email]" and say so. Never invent one | |
| experience | array | – | Roles in any order you like -- profile_set sorts and stores them newest-first (an open role with no `end` first, then by `end` descending, then by `start` descending) before saving, since page-budget… |
| languages | array | – | – |
| links | array | – | Portfolio, LinkedIn, GitHub |
| location | string | – | – |
| merge | boolean | – | Update the stored profile: fields you pass replace their stored value, fields you leave out are kept. Required when a profile already exists, unless you pass replace |
| name | string | – | Your own name. Leave it out and the shared business profile's name is used, so you are never asked for a name the suite already holds |
| phone | string | – | Your own phone number. Defaults to the shared business profile's phone |
| replace | boolean | – | Discard the stored profile and store exactly what this call carries. Required when a profile already exists, unless you pass merge |
| skills | array | – | – |
| summary | string | – | Two or three lines. Used verbatim as the fit paragraph of a cover letter. |
| variant | string | – | Name a second profile, e.g. "backend". One profile per data directory on the free tier; named variants are Pro only. |
No output schema declared.
No examples provided.
resume_create Write a resume .docx ~237
Call this tool to write the stored profile to a Word .docx. Returns the output path, the estimated page count, which bullets were dropped to fit, and which keywords matched or are missing.
| Name | Type | Req | Description |
|---|---|---|---|
| keywords | array | – | From the posting. A keyword that appears anywhere in the profile is printed in bold; one that does not is reported as missing and is never added to the resume. |
| max_pages | integer | – | Bullets are ordered by relevance to target_role and keywords, then trimmed to fit this many pages against a measured word budget. Default 2. |
| out_path | string | – | Where to write the .docx. Defaults to <data dir>/documents/<name>-resume.docx, numbered -2, -3, ... if that exists. |
| overwrite | boolean | – | Replace an existing file at out_path. Default false: the call fails and nothing is written. |
| style | string | – | Free tier prints "modern" only; "classic" and "compact" are Pro. |
| target_role | string | – | Printed under your name and used to rank bullets |
| variant | string | – | – |
No output schema declared.
No examples provided.
resume_read Read an existing resume .docx ~120
Call this tool to read an existing .docx resume into the profile shape, with the sections found and anything unplaced. It saves nothing unless save is true, so review it first. .doc and .rtf are refused.
| Name | Type | Req | Description |
|---|---|---|---|
| docx_base64 | string | – | The .docx itself, base64-encoded, instead of uploading it first |
| path | string | – | Name of a document uploaded with doc_upload |
| save | boolean | – | Store the result as the profile. Review it first. |
| variant | string | – | – |
No output schema declared.
No examples provided.
resume_to_html Printable resume HTML ~162
Call this tool to write the resume as semantic HTML with a print stylesheet and return where it went; print it to PDF from a browser, because there is no doc_to_pdf here. Bullets are trimmed to fit max_pages. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| max_pages | integer | – | Bullets are trimmed to fit this many pages against a measured word budget. Default 2. |
| out_path | string | – | Where to write the .html. Defaults to <data dir>/documents/<name>-resume.html, numbered -2, -3, ... if that exists. |
| overwrite | boolean | – | Replace an existing file at out_path. Default false: the call fails and nothing is written. |
| target_role | string | – | – |
| variant | string | – | – |
No output schema declared.
No examples provided.
resume_to_markdown Resume as markdown ~72
Return the stored profile as markdown text inline, ready to paste into a form or an ATS box. Same page-budget trimming as resume_create for max_pages. Nothing is written to disk. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| max_pages | integer | – | – |
| target_role | string | – | – |
| variant | string | – | – |
No output schema declared.
No examples provided.
tailor_to_job Gap analysis against a posting ~104
READ-ONLY gap analysis against a posting: writes nothing, changes nothing. Returns matched keywords, missing ones, a coverage figure and orderings of facts you already stated. Act on it with resume_create.
| Name | Type | Req | Description |
|---|---|---|---|
| job_description | string | yes | Paste the posting. The free tier reads up to 2,000 characters; Pro reads any length. |
| limit | integer | – | How many keywords to extract from the posting. Default 30. |
| variant | string | – | – |
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/resume-cover-letter-docx-generator MCP server?
io.github.theluckystrike/resume-cover-letter-docx-generator is an MCP server listed in the public MCP registry as io.github.theluckystrike/resume-cover-letter-docx-generator. Tailor a resume and write a cover letter as real Word .docx files from facts you stored once. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/resume).
Is the io.github.theluckystrike/resume-cover-letter-docx-generator MCP server safe to use?
io.github.theluckystrike/resume-cover-letter-docx-generator scores 81 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/resume-cover-letter-docx-generator MCP server expose?
io.github.theluckystrike/resume-cover-letter-docx-generator exposes 13 tools: profile_set, profile_get, resume_create, resume_to_markdown, resume_to_html, and 8 more. Their descriptions and schemas cost roughly 1,898 tokens of context every time the server is loaded.
Does the io.github.theluckystrike/resume-cover-letter-docx-generator MCP server require authentication?
Yes. io.github.theluckystrike/resume-cover-letter-docx-generator 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/resume-cover-letter-docx-generator MCP server still maintained?
io.github.theluckystrike/resume-cover-letter-docx-generator 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.