McpStamp Resume and Cover Letter
MCPB · RESUME.MCPB · 2 COMPONENTS
Store your CV once, then get tailored .docx resumes, cover letters and keyword gaps for a job.
Available components
Last scanned (4 hours ago)
Scores higher than 94% of MCPB servers
Category Documents and Files
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
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 113 of 113 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 43 of 113 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 48 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- 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 1539 tokens (~139/item across 11 items; 10 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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.
- 2 Nov 26 +56
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Schema quality: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Dependency health: unverified → 0.83 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- Package version: 0.22.5 → 0.21.0 functional
- 23 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 19 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 18 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 16 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 15 Oct 26 0
- Tool safety: Tool safety not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no tool text to scan. security
- Stability: Stability not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no schema to compare. security
- Schema quality: Schema quality not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no schema to assess. functional
- Capabilities: Protocol version not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we never saw its MCP handshake. functional
- Tool coverage: Tool coverage not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no tool definitions to assess. functional
- 14 Oct 26 0
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.22.1 → 0.22.5 functional
- 13 Oct 26 0
- Stability: Stability not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no schema to compare. security
- Tool safety: Tool safety not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no tool text to scan. security
- Capabilities: Protocol version not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we never saw its MCP handshake. functional
- Schema quality: Schema quality not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no schema to assess. functional
- Tool coverage: Tool coverage not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no tool definitions to assess. functional
- Package version: 0.22.0 → 0.22.1 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 5 Nov 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/resume.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 |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 113 packages
| Packages resolved | 113 |
|---|---|
| Stale | 43 |
| 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 →
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.
license_activate Activate license ~71
Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.
| 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 ~54
Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.
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 ~121
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 |
|---|---|---|---|
| path | string | yes | 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 | – | – |
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.
How do I install the McpStamp Resume and Cover Letter MCP server?
McpStamp Resume and Cover Letter ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 38519bcf2230a67e344f515d917091816defac0854851037c50318807722d4d4; the commands to do that are on this page. If it does not match, do not open it.
mcpb · resume.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
38519bcf2230a67e344f515d917091816defac0854851037c50318807722d4d4
macOS / Linux
echo "38519bcf2230a67e344f515d917091816defac0854851037c50318807722d4d4 resume.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\resume.mcpb).Hash -eq "38519bcf2230a67e344f515d917091816defac0854851037c50318807722d4d4"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the McpStamp Resume and Cover Letter MCP server?
McpStamp Resume and Cover Letter is an MCP server listed in the public MCP registry as io.github.theluckystrike/resume-cover-letter-docx-generator. Store your CV once, then get tailored .docx resumes, cover letters and keyword gaps for a job. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/resume.mcpb).
Is the McpStamp Resume and Cover Letter MCP server safe to use?
McpStamp Resume and Cover Letter scores 61 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 McpStamp Resume and Cover Letter MCP server expose?
McpStamp Resume and Cover Letter 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,515 tokens of context every time the server is loaded.
What licence is the McpStamp Resume and Cover Letter MCP server under?
McpStamp Resume and Cover Letter declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.