# io.github.theluckystrike/career (mcpb · resume.mcpb)

Tailor a career resume and cover letter as real Word docx files from stored facts.

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

## Components

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

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/resume.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 12 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/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 1425 tokens (~129/item across 11 items; 10 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**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 63% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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/resume.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-20 (score 54, +1)

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

### 2026-09-18 (score 53, +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.

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

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

### 2026-09-14 (score 51, +3)

- [functional improvement] Stability: unverified → 0.23

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

First indexed and scored.

## MCP tools (10)

### `profile_set` (~414 tokens)

Store your CV facts

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.

Input parameters:

- `accent_color` (string): Letterhead colour, six hex digits, e.g. 1F3864. Pro only.
- `certifications` (array)
- `education` (array)
- `email` (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.

### `profile_get` (~40 tokens)

Show the stored profile

Return the stored profile as JSON, exactly as it will be used by resume_create, cover_letter_create and tailor_to_job.

Input parameters:

- `variant` (string)

### `resume_create` (~237 tokens)

Write a resume .docx

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.

Input parameters:

- `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)

### `resume_to_markdown` (~53 tokens)

Resume as markdown

Return the stored profile as markdown: paste it into a form, an email or an ATS box.

Input parameters:

- `max_pages` (integer)
- `target_role` (string)
- `variant` (string)

### `resume_to_html` (~146 tokens)

Printable resume HTML

Call this tool to write the resume as semantic HTML with a print stylesheet. Returns the output path. Open the file in a browser and print it to PDF.

Input parameters:

- `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)

### `resume_read` (~116 tokens)

Read an existing resume .docx

Call this tool to extract an existing Word resume into the profile shape: name, contact, summary, skills, roles with bullets, education. Returns the parsed profile, the sections found, and anything unparsed.

Input parameters:

- `path` (string, required): Path to an existing .docx. Legacy .doc and .rtf are not readable here. Parsed best effort, section by heading.
- `save` (boolean): Store the result as the profile. Default false: nothing is saved. Review the result first.
- `variant` (string)

### `cover_letter_create` (~226 tokens)

Write a cover letter .docx

Call this tool to write a one-page cover letter from the stored profile: opening, fit, proof, close. Returns the output path, the word count, and every bracketed prompt left for you to fill in.

Input parameters:

- `company` (string, required)
- `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, required)
- `tone` (string): Default "formal".

### `tailor_to_job` (~104 tokens)

Gap analysis against a posting

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.

Input parameters:

- `job_description` (string, required): 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)

### `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-career/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-resume-mcp#diagnostics

## Score history

- 2026-09-20: 54
- 2026-09-19: 53
- 2026-09-18: 53
- 2026-09-17: 52
- 2026-09-16: 52
- 2026-09-15: 51
- 2026-09-14: 51
- 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/career MCP server?

io.github.theluckystrike/career is an MCP server listed in the public MCP registry as io.github.theluckystrike/career. Tailor a career resume and cover letter as real Word docx files from stored facts. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/resume.mcpb).

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

io.github.theluckystrike/career 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/career MCP server expose?

io.github.theluckystrike/career exposes 10 tools: profile_set, profile_get, resume_create, resume_to_markdown, resume_to_html, and 5 more. Their descriptions and schemas cost roughly 1,401 tokens of context every time the server is loaded.

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

io.github.theluckystrike/career 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/resume
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-career/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-resume-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-career/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-resume-mcp.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-career/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-resume-mcp