Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.theluckystrike/resume-builder-ats-checker

REMOTE · MCP.ZOVO.ONE

Build an ATS-friendly resume and check it against a job description, fully offline.

Available components

−13 this week 80 Trust /100

Last scanned (20 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Documents and Files

Recent critical change

Authorization (17 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
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 2119 tokens (~141/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 Management95
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 0 breaking changes, 1 auth/transport breaks, 0 additions. See how to fix → Fail
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 15 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 17 Nov 26 −13
    • Authorization: pass → fail ▼ critical
    • Stability: pass → fail ▼ security
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “doc_delete_upload” is now declared destructive security
    • Tool “doc_upload” is now declared destructive security
    • Destructive annotations: All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
Diagnostics

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 21 Nov 2026 · Probed https://mcp.zovo.one/mcp/resume-builder-ats-checker

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 31 Oct 2026 29 Jan 2027 ECDSA 256 ECDSA-SHA256 39e1adfa4eb6500e0e3d48868766e3e9
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. DS published 64939 8 Verified
zovo.one. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
x-content-type-options nosniff

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-builder-ats-checker Verified 200
http (plaintext) http://mcp.zovo.one/mcp/resume-builder-ats-checker HTTPS enforced 301 https://mcp.zovo.one/mcp/resume-builder-ats-checker
MCP tools · 13 exposed · ~1,898 tokens

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 →

Tool Tokens
cover_letter_create ~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.

NameTypeReqDescription
companystringyes–
highlightsarray–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_managerstring––
job_descriptionstring–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_pathstring–Where to write the .docx. Defaults to <data dir>/documents/<company>-<role>-cover-letter.docx, numbered -2, -3, ... if that exists.
overwriteboolean–Replace an existing file at out_path. Default false: the call fails and nothing is written.
rolestringyes–
tonestring–Default "formal".

No output schema declared.

No examples provided.

doc_delete_upload ~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.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

doc_files ~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 ~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.

NameTypeReqDescription
docx_base64string–The .docx file, base64-encoded
namestringyesName to refer to this document by: 1-64 characters of letters, digits, underscore or dash, e.g. "contract"
urlstring–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 ~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.

NameTypeReqDescription
keystringyesLicense key from checkout, MCPL1.<payload>.<signature>

No output schema declared.

No examples provided.

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 ~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.

NameTypeReqDescription
variantstring––

No output schema declared.

No examples provided.

profile_set ~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.

NameTypeReqDescription
accent_colorstring–Letterhead colour, six hex digits, e.g. 1F3864. Pro only.
certificationsarray––
educationarray––
emailstring–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
experiencearray–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…
languagesarray––
linksarray–Portfolio, LinkedIn, GitHub
locationstring––
mergeboolean–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
namestring–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
phonestring–Your own phone number. Defaults to the shared business profile's phone
replaceboolean–Discard the stored profile and store exactly what this call carries. Required when a profile already exists, unless you pass merge
skillsarray––
summarystring–Two or three lines. Used verbatim as the fit paragraph of a cover letter.
variantstring–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 ~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.

NameTypeReqDescription
keywordsarray–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_pagesinteger–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_pathstring–Where to write the .docx. Defaults to <data dir>/documents/<name>-resume.docx, numbered -2, -3, ... if that exists.
overwriteboolean–Replace an existing file at out_path. Default false: the call fails and nothing is written.
stylestring–Free tier prints "modern" only; "classic" and "compact" are Pro.
target_rolestring–Printed under your name and used to rank bullets
variantstring––

No output schema declared.

No examples provided.

resume_read ~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.

NameTypeReqDescription
docx_base64string–The .docx itself, base64-encoded, instead of uploading it first
pathstring–Name of a document uploaded with doc_upload
saveboolean–Store the result as the profile. Review it first.
variantstring––

No output schema declared.

No examples provided.

resume_to_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.

NameTypeReqDescription
max_pagesinteger–Bullets are trimmed to fit this many pages against a measured word budget. Default 2.
out_pathstring–Where to write the .html. Defaults to <data dir>/documents/<name>-resume.html, numbered -2, -3, ... if that exists.
overwriteboolean–Replace an existing file at out_path. Default false: the call fails and nothing is written.
target_rolestring––
variantstring––

No output schema declared.

No examples provided.

resume_to_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.

NameTypeReqDescription
max_pagesinteger––
target_rolestring––
variantstring––

No output schema declared.

No examples provided.

tailor_to_job ~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.

NameTypeReqDescription
job_descriptionstringyesPaste the posting. The free tier reads up to 2,000 characters; Pro reads any length.
limitinteger–How many keywords to extract from the posting. Default 30.
variantstring––

No output schema declared.

No examples provided.

Install

How do I install the io.github.theluckystrike/resume-builder-ats-checker MCP server?

io.github.theluckystrike/resume-builder-ats-checker is a hosted endpoint at https://mcp.zovo.one/mcp/resume-builder-ats-checker, 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

# add to Claude Code
claude mcp add --transport http theluckystrike-resume-builder-ats-checker 'https://mcp.zovo.one/mcp/resume-builder-ats-checker'
Common questions

What is the io.github.theluckystrike/resume-builder-ats-checker MCP server?

io.github.theluckystrike/resume-builder-ats-checker is an MCP server listed in the public MCP registry as io.github.theluckystrike/resume-builder-ats-checker. Build an ATS-friendly resume and check it against a job description, fully offline. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/resume-builder-ats-checker).

Is the io.github.theluckystrike/resume-builder-ats-checker MCP server safe to use?

io.github.theluckystrike/resume-builder-ats-checker scores 80 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-builder-ats-checker MCP server expose?

io.github.theluckystrike/resume-builder-ats-checker 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-builder-ats-checker MCP server require authentication?

No. We connected to io.github.theluckystrike/resume-builder-ats-checker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.theluckystrike/resume-builder-ats-checker MCP server still maintained?

io.github.theluckystrike/resume-builder-ats-checker is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.theluckystrike/resume-builder-ats-checker MCP server?

VerifyMCP ran 13 checks on io.github.theluckystrike/resume-builder-ats-checker, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.