Skip to content

McpStamp Resume and Cover Letter MCP server

io.github.theluckystrike/resume-cover-letter-docx-generatortheluckystrikestreamable-httpv0.23.0Scanned

Store your CV once, then get tailored .docx resumes, cover letters and keyword gaps for a job.

13 tools: 2 can delete or cancel things, 7 change things and 4 only read.

Tools: 2 delete, 0 irreversible, 7 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 1
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the McpStamp Resume and Cover Letter MCP server can do

The McpStamp Resume and Cover Letter MCP server is published by the GitHub account theluckystrike. It has 13 tools. It can delete or cancel things (2 tools: doc_upload and doc_delete_upload) and create or change data (7 tools: profile_set, resume_create, resume_to_markdown, resume_to_html and 3 more). 4 tools only read.

1 tool reads private data (doc_files); 1 tool brings in text other people can write (license_status); 1 tool can send data out of your system (profile_set). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 0.23.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Deletes or cancels 2Claude Code: deny
  • doc_delete_uploadDelete one document uploaded for your token: name is the name it was uploaded under, without .docx.No findings

    Why it is in this group

    • The name "doc_delete_upload" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • doc_uploadSend an existing Word document to this hosted endpoint.No findings

    Why it is in this group

    • The name "doc_upload" says "upload": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 7Claude Code: ask
  • cover_letter_createCall this tool to write a one-page cover letter .docx from the stored profile and return the path, word count and bracketed prompts.No findings

    Why it is in this group

    • The name "cover_letter_create" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • license_activateTurn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • profile_setStore the profile every resume and cover letter is built from: contact details, summary, skills, roles with bullets, education, certifications and languages.Can send data outNo findings

    Why it is in this group

    • The name "profile_set" says "set": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • resume_createCall this tool to write the stored profile to a Word .docx.No findings

    Why it is in this group

    • The name "resume_create" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • resume_readCall this tool to read an existing .docx resume into the profile shape, with the sections found and anything unplaced.1 finding

    Why it is in this group

    • The name "resume_read" says "read": a word for reading.
    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "resume_read" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "resume_read" says "read": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • resume_to_htmlCall 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.No findings

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • resume_to_markdownReturn the stored profile as markdown text inline, ready to paste into a form or an ATS box.1 finding

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "resume_to_markdown" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "return": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • doc_filesList the documents uploaded for your token, with their sizes.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.

    What it can reach

    • private-dataThe name "doc_files" says "doc": it reads documents.
    • private-dataThe description's first sentence says "list" and "document": it reads documents.
    Description, as the server wrote it
    List the documents uploaded for your token, with their sizes.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • license_statusReport 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.Reads text others writeNo findings

    Why it is in this group

    • The name "license_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • profile_getReturn 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.No findings

    Why it is in this group

    • The name "profile_get" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • tailor_to_jobREAD-ONLY gap analysis against a posting: writes nothing, changes nothing.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

1 path in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__resume-cover-letter-docx-generator__profile_set"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:35 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
9
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/resume
Authorization servers
https://mcp.zovo.one
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 9 tools that change things (2 destructive, 7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.zovo.one/mcp/resume: tools/list returned 13 tools to an anonymous client, including doc_upload (destructive), doc_delete_upload (destructive), profile_set (write), resume_create (write), resume_to_markdown (write) and 4 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • HTTP status of an anonymous initialize: 429 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 9
    • Protocol version: none to 2025-06-18
  2. Nov 6, 2026
    • RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/resume
  3. Oct 29, 2026
    • HTTP status of an anonymous initialize: 200 to 429
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 10 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "resume_to_markdown" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "return": a word for reading.

    What this check looks for
  • The server marks "resume_read" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "resume_read" says "read": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 429 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 9 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 429 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 9
    • Protocol version: none to 2025-06-18
  2. PostureRemote posture changed. RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource -> https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/resume.View diff
    • RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/resume
  3. Tools4 changed.~4 changedView diff
  4. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 429; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 10 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 429
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 10 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 0.23.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http resume-cover-letter-docx-generator https://mcp.zovo.one/mcp/resume
claude mcp add --transport http resume-cover-letter-docx-generator https://mcp.zovo.one/mcp/resume

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__resume-cover-letter-docx-generator__profile_get",
      "mcp__resume-cover-letter-docx-generator__tailor_to_job",
      "mcp__resume-cover-letter-docx-generator__license_status",
      "mcp__resume-cover-letter-docx-generator__doc_files"
    ],
    "ask": [
      "mcp__resume-cover-letter-docx-generator__profile_set",
      "mcp__resume-cover-letter-docx-generator__resume_create",
      "mcp__resume-cover-letter-docx-generator__resume_to_markdown",
      "mcp__resume-cover-letter-docx-generator__resume_to_html",
      "mcp__resume-cover-letter-docx-generator__resume_read",
      "mcp__resume-cover-letter-docx-generator__cover_letter_create",
      "mcp__resume-cover-letter-docx-generator__license_activate"
    ],
    "deny": [
      "mcp__resume-cover-letter-docx-generator__doc_upload",
      "mcp__resume-cover-letter-docx-generator__doc_delete_upload"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as resume-cover-letter-docx-generator. Review it before you use it.

Capability tags behind 3 rules
  • mcp__resume-cover-letter-docx-generator__profile_set outbound
  • mcp__resume-cover-letter-docx-generator__license_status untrusted-input
  • mcp__resume-cover-letter-docx-generator__doc_files private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.theluckystrike/resume-cover-letter-docx-generator/verify?hash=e7f73405f70be7099f23e7ea0afa08f97a1afe43ce013a73683b48516e7eb552" | jq -e '.changed == false'

Pinned hash e7f73405f70b, from Nov 15, 2026, 06:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.theluckystrike/resume-cover-letter-docx-generator/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.theluckystrike/resume-cover-letter-docx-generator
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.theluckystrike/resume-cover-letter-docx-generator.svg)](https://radar.anlyon.com/servers/io.github.theluckystrike/resume-cover-letter-docx-generator)

Source: MCP Registry · repository. Synced Nov 2, 2026, 03:18 UTC.

McpStamp Resume and Cover Letter MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the McpStamp Resume and Cover Letter MCP server safe?

No scan can promise that. What its definitions show: 13 tools, 9 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the McpStamp Resume and Cover Letter MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: doc_upload and doc_delete_upload.

Can the McpStamp Resume and Cover Letter MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the McpStamp Resume and Cover Letter MCP server have?

13 tools: 2 destructive, 7 write, 4 read. doc_upload, doc_delete_upload, profile_set, resume_create, resume_to_markdown, resume_to_html, resume_read, cover_letter_create and 5 more.

Does the McpStamp Resume and Cover Letter MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the McpStamp Resume and Cover Letter MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): profile_set.

Has the McpStamp Resume and Cover Letter MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 2, 2026. Every change is on this page and in its Atom feed.