io.github.vpatser1/resume-optimizer
NPM · RESUME-OPTIMIZER
Resume analysis, ATS compatibility checks, bullet improvements, job-tailored optimization
Available components
Last scanned (13 hours ago)
Scores higher than 51% of npm servers
Category Productivity and Notes
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 109 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 631 tokens (~105/item across 6 items; 6 tools + 0 resources), lean.Pass
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 +1
- Stability: 0.97 → pass security
- 17 Nov 26 −1
- Stability: pass → 0.93 functional
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Nov 26 −3
- Stability: pass → 0.80 functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Oct 26 −1
- Stability: pass → 0.97 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 21 Nov 2026 · Analysed npm/resume-optimizer@1.1.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| 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 →
analyze_keywords ~113
Extract and analyze keywords from resume text. Identifies hard skills, soft skills, tools/technologies, certifications, and action verbs. Assesses industry relevance and keyword density. Optionally target a specific industry (tech, finance, marketing, healthcare) for tailored analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | – | Target industry for keyword relevance (e.g., 'tech', 'finance', 'marketing', 'healthcare'). Defaults to general. |
| resume_text | string | yes | The full text content of the resume to analyze for keywords |
No output schema declared.
No examples provided.
analyze_resume ~106
Perform a comprehensive resume analysis. Returns an overall score (0-100), ATS compatibility score, keyword density analysis, action verb usage, quantified achievements count, section completeness check (contact, summary, experience, education, skills), formatting/structure issues, and length assessment. Optionally score against a job description for keyword relevance.
| Name | Type | Req | Description |
|---|---|---|---|
| job_description | string | – | Optional job description to score keyword relevance against |
| resume_text | string | yes | The full text content of the resume to analyze |
No output schema declared.
No examples provided.
check_ats ~91
Deep ATS (Applicant Tracking System) compatibility check. Validates font/formatting recommendations, section header standardization, file format advice, keyword stuffing detection, and contact info parsing. Returns categorized issues (error/warning/info) with fix suggestions, detected vs missing sections, and an overall ATS-readiness rating.
| Name | Type | Req | Description |
|---|---|---|---|
| resume_text | string | yes | The full text content of the resume to check for ATS compatibility |
No output schema declared.
No examples provided.
generate_summary ~108
Generate 2-3 sentence professional summary options from resume text. Produces multiple variants -- confident, technical, and leadership-focused -- tailored to the detected career level (entry/mid/senior/executive). Optionally target a specific role for more focused output.
| Name | Type | Req | Description |
|---|---|---|---|
| resume_text | string | yes | The full text content of the resume to generate a summary from |
| target_role | string | – | The target job title or role to tailor the summary toward (e.g., 'Engineering Manager') |
No output schema declared.
No examples provided.
improve_bullets ~116
Analyze resume bullet points and rewrite them for maximum impact. Checks each bullet for action verb usage, quantified results, specificity, STAR method format (Situation, Task, Action, Result), and appropriate length. Returns before/after comparisons with per-bullet scores and rewrite suggestions using stronger action verbs and quantification.
| Name | Type | Req | Description |
|---|---|---|---|
| bullets | array | yes | Array of bullet point strings to analyze and improve |
| context | string | – | Optional context about the role or industry for more relevant suggestions (e.g., 'software engineering', 'marketing manager') |
No output schema declared.
No examples provided.
optimize_for_job ~97
Match a resume against a specific job description. Identifies matching keywords, finds missing keywords from the job description, suggests bullet point rewrites to match job requirements, calculates a match score (0-100), and highlights transferable skills. Returns detailed gap analysis and actionable improvement suggestions.
| Name | Type | Req | Description |
|---|---|---|---|
| job_description | string | yes | The full text of the job description to optimize against |
| resume_text | string | yes | The full text content of the resume |
No output schema declared.
No examples provided.
How do I install the io.github.vpatser1/resume-optimizer MCP server?
io.github.vpatser1/resume-optimizer runs locally as an npm package, launched with npx -y resume-optimizer. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · resume-optimizer
claude mcp add vpatser1-resume-optimizer -- npx -y resume-optimizer
What is the io.github.vpatser1/resume-optimizer MCP server?
io.github.vpatser1/resume-optimizer is an MCP server listed in the public MCP registry as io.github.vpatser1/resume-optimizer. Resume analysis, ATS compatibility checks, bullet improvements, job-tailored optimization. This page covers its npm package (resume-optimizer).
Is the io.github.vpatser1/resume-optimizer MCP server safe to use?
io.github.vpatser1/resume-optimizer scores 75 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. 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.vpatser1/resume-optimizer MCP server expose?
io.github.vpatser1/resume-optimizer exposes 6 tools: analyze_resume, optimize_for_job, generate_summary, improve_bullets, check_ats, analyze_keywords. Their descriptions and schemas cost roughly 631 tokens of context every time the server is loaded.
Is the io.github.vpatser1/resume-optimizer MCP server still maintained?
io.github.vpatser1/resume-optimizer 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 licence is the io.github.vpatser1/resume-optimizer MCP server under?
io.github.vpatser1/resume-optimizer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.vpatser1/resume-optimizer MCP server?
VerifyMCP ran 15 checks on io.github.vpatser1/resume-optimizer, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.vpatser1/resume-optimizer: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.