CV Forge
NPM · CV-FORGE · SCANNED OCT 1
Forge powerful, ATS-friendly CVs tailored to any job - an MCP server for intelligent CV generation
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 94 of 250 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency43
- 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 338 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 731 tokens (~66/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% 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 11 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
How do I install the CV Forge MCP server?
CV Forge runs locally as an npm package, launched with npx -y cv-forge. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · cv-forge
claude mcp add thechandanbhagat-cv-forge -- npx -y cv-forge
{
"mcpServers": {
"thechandanbhagat-cv-forge": {
"command": "npx",
"args": [
"-y",
"cv-forge"
]
}
}
} {
"servers": {
"thechandanbhagat-cv-forge": {
"command": "npx",
"args": [
"-y",
"cv-forge"
]
}
}
} codex mcp add thechandanbhagat-cv-forge -- npx -y cv-forge
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"thechandanbhagat-cv-forge": {
"type": "local",
"command": [
"npx",
"-y",
"cv-forge"
],
"enabled": true
}
}
} openclaw mcp add thechandanbhagat-cv-forge --command npx --arg -y --arg cv-forge
mcp_servers:
thechandanbhagat-cv-forge:
command: "npx"
args: ["-y", "cv-forge"] {
"McpServers": {
"thechandanbhagat-cv-forge": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"cv-forge"
]
}
}
} assistant mcp add thechandanbhagat-cv-forge -t stdio -c npx -a -y cv-forge
{
"mcpServers": {
"thechandanbhagat-cv-forge": {
"command": "npx",
"args": [
"-y",
"cv-forge"
]
}
}
} 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.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 −2
- Stability: pass → 0.80 functional
- 25 Sept 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 21 Sept 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.
- 19 Sept 26 −2
- Stability: pass → 0.80 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 1 Oct 2026 · Analysed npm/cv-forge@1.0.1
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 →
Dependencies 250 packages
| Packages resolved | 250 |
|---|---|
| Stale | 94 |
| 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 →
debug_cv_data ~32
Debug tool to inspect the structure of CV data
| Name | Type | Req | Description |
|---|---|---|---|
| cvData | – | – | Tailored CV data object to inspect |
No output schema declared.
No examples provided.
generate_and_save_cv_html ~76
Generate tailored CV and save directly as HTML (combines CV generation and HTML creation in one step)
| Name | Type | Req | Description |
|---|---|---|---|
| fileName | string | – | Custom filename (without extension) |
| jobRequirements | object | yes | – |
| outputPath | string | yes | Directory path where the CV should be saved |
| userProfile | object | yes | – |
No output schema declared.
No examples provided.
generate_and_save_cv_markdown ~77
Generate tailored CV and save directly as Markdown (combines CV generation and Markdown creation in one step)
| Name | Type | Req | Description |
|---|---|---|---|
| fileName | string | – | Custom filename (without extension) |
| jobRequirements | object | yes | – |
| outputPath | string | yes | Directory path where the CV should be saved |
| userProfile | object | yes | – |
No output schema declared.
No examples provided.
generate_and_save_cv_pdf ~100
Generate tailored CV and save directly as PDF (combines CV generation and PDF creation in one step). If outputPath is not provided, uses DEFAULT_OUTPUT_PATH from environment.
| Name | Type | Req | Description |
|---|---|---|---|
| fileName | string | – | Custom filename (without extension) |
| jobRequirements | object | yes | – |
| outputPath | string | – | Directory path where the CV should be saved (optional, uses DEFAULT_OUTPUT_PATH if not provided) |
| userProfile | object | yes | – |
No output schema declared.
No examples provided.
generate_cv_data ~41
Generate tailored CV content based on user profile and job requirements (returns structured data)
| Name | Type | Req | Description |
|---|---|---|---|
| jobRequirements | object | yes | – |
| userProfile | object | yes | – |
No output schema declared.
No examples provided.
generate_cv_html ~59
Generate CV as styled HTML document for web viewing
| Name | Type | Req | Description |
|---|---|---|---|
| cvData | – | – | Tailored CV data object |
| fileName | string | – | Custom filename (without extension) |
| outputPath | string | yes | Directory path where the CV should be saved |
No output schema declared.
No examples provided.
generate_cv_markdown ~62
Generate CV as Markdown format for easy editing and version control
| Name | Type | Req | Description |
|---|---|---|---|
| cvData | – | – | Tailored CV data object |
| fileName | string | – | Custom filename (without extension) |
| outputPath | string | yes | Directory path where the CV should be saved |
No output schema declared.
No examples provided.
generate_cv_pdf ~59
Generate and save CV as a professional PDF document
| Name | Type | Req | Description |
|---|---|---|---|
| cvData | – | – | Tailored CV data object |
| fileName | string | – | Custom filename (without extension) |
| outputPath | string | yes | Directory path where the CV should be saved |
No output schema declared.
No examples provided.
generate_cv_to_default_folder ~65
Generate tailored CV and save to default folder (uses .env DEFAULT_OUTPUT_PATH)
| Name | Type | Req | Description |
|---|---|---|---|
| fileName | string | – | Custom filename (without extension) |
| format | string | – | Output format |
| jobRequirements | object | yes | – |
| userProfile | object | yes | – |
No output schema declared.
No examples provided.
parse_job_requirements ~99
Parse job requirements and extract key information for CV tailoring
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company name |
| jobDescription | string | yes | Full job description text |
| jobTitle | string | yes | The job title/position |
| location | string | – | Job location |
| preferredSkills | array | – | Preferred skills if separated |
| requirements | array | – | Specific requirements if separated |
| salaryRange | string | – | Salary range if provided |
No output schema declared.
No examples provided.
save_cv_text ~61
Save CV content as a text file to specified location
| Name | Type | Req | Description |
|---|---|---|---|
| cvData | – | – | Tailored CV data object |
| fileName | string | – | Optional custom filename (without extension) |
| outputPath | string | yes | Directory path where the CV should be saved |
No output schema declared.
No examples provided.
What is the CV Forge MCP server?
CV Forge is an MCP server listed in the public MCP registry as io.github.thechandanbhagat/cv-forge. Forge powerful, ATS-friendly CVs tailored to any job - an MCP server for intelligent CV generation. This page covers its npm package (cv-forge).
Is the CV Forge MCP server safe to use?
CV Forge scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 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 CV Forge MCP server expose?
CV Forge exposes 11 tools: parse_job_requirements, generate_cv_data, generate_and_save_cv_pdf, save_cv_text, generate_cv_pdf, and 6 more. Their descriptions and schemas cost roughly 731 tokens of context every time the server is loaded.
Is the CV Forge MCP server still maintained?
CV Forge is still listed as active in the MCP registry. We last reached this channel on 1 October 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 CV Forge MCP server under?
CV Forge declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.