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.18boys/matchcv

NPM · MATCHCV-MCP · SCANNED SEP 20

ATS resume checking, job description analysis, and AI resume tailoring powered by MatchCV.

Available components

+4 this week 80 Trust /100
Trust breakdown (7 categories)

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
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 774 tokens (~129/item across 6 items; 6 tools + 0 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 Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 7 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
Install

How do I install the io.github.18boys/matchcv MCP server?

io.github.18boys/matchcv runs locally as an npm package, launched with npx -y matchcv-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · matchcv-mcp

# add to Claude Code
claude mcp add 18boys-matchcv -- npx -y matchcv-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "18boys-matchcv": {
      "command": "npx",
      "args": [
        "-y",
        "matchcv-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "18boys-matchcv": {
      "command": "npx",
      "args": [
        "-y",
        "matchcv-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add 18boys-matchcv -- npx -y matchcv-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "18boys-matchcv": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "matchcv-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add 18boys-matchcv --command npx --arg -y --arg matchcv-mcp
# ~/.hermes/config.yaml
mcp_servers:
  18boys-matchcv:
    command: "npx"
    args: ["-y", "matchcv-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "18boys-matchcv": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "matchcv-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add 18boys-matchcv -t stdio -c npx -a -y matchcv-mcp
// mcp.json
{
  "mcpServers": {
    "18boys-matchcv": {
      "command": "npx",
      "args": [
        "-y",
        "matchcv-mcp"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +4
    • Stability: unverified → 0.27 functional
  • 31 Aug 26 70

    First indexed and scored.

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 20 Sept 2026 · Analysed npm/matchcv-mcp@0.1.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 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~674 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
analyze_job_description ~63

Parse a job posting into structured data: title, company, seniority, industry, must-have keywords, nice-to-have keywords, and key responsibilities. Feed the result into optimize_resume to find keyword gaps.

NameTypeReqDescription
jdTextstringyesThe full job description text.

No output schema declared.

No examples provided.

ats_check ~91

Score resume text for applicant tracking system (ATS) compatibility. Returns a 0-100 score, a recruiter take, prioritized issues with concrete fixes, and detected strengths. Use for "is my resume ATS friendly", "why am I not getting interviews", or before tailoring to a specific job.

NameTypeReqDescription
resumeTextstringyesFull plain-text resume. Use extract_resume_text first if you only have a file.

No output schema declared.

No examples provided.

extract_resume_text ~135

Read a local PDF/DOC/DOCX/TXT resume and return its plain text, optionally also parsing it into structured JSON (name, experience, education, skills). Text extraction is unlimited; set structured=true only when the structured form is needed, since that path uses a daily AI credit. Scanned/image-only PDFs will fail — ask the user to paste the text instead.

NameTypeReqDescription
filePathstringyesPath to the resume file on this machine (absolute, or relative to the CWD).
structuredbooleanAlso return AI-parsed structured resume JSON. Costs one daily AI credit. Defaults to false.

No output schema declared.

No examples provided.

optimize_resume ~139

Return prioritized, rewrite-level suggestions for a resume, optionally aimed at a specific role or job description. Each suggestion has a type, priority, tip, and an example rewrite. Pass missingMustHave / missingNiceToHave from analyze_job_description to close keyword gaps.

NameTypeReqDescription
jdTextstringTarget job description, for role-specific suggestions.
jobTitlestringTarget job title, e.g. "Senior Backend Engineer".
missingMustHavearrayRequired keywords the resume is missing.
missingNiceToHavearrayPreferred keywords the resume is missing.
resumeTextstringyesFull plain-text resume.

No output schema declared.

No examples provided.

roast_resume ~75

Run the MatchCV "resume roast": a brutally honest recruiter reaction plus an ATS score. Returns a public shareable report URL. Use when the user wants candid feedback rather than a polite checklist.

NameTypeReqDescription
jobTitlestringTarget job title to judge the resume against.
resumeTextstringyesFull plain-text resume.

No output schema declared.

No examples provided.

tailor_resume ~171

The full MatchCV pipeline: analyze the job description, structure the resume, then rewrite it for that role with must-have keywords worked in and bullets rewritten. Returns the tailored resume JSON, an ATS score, and a public preview link the user can open and download as PDF. This is the heaviest tool — it uses one generation credit plus the parse and JD-analysis credits, so run it once the user has settled on a target job.

NameTypeReqDescription
jdTextstringyesThe target job description.
resumeTextstringyesThe candidate's current resume as plain text.
targetLanguagestring"en" forces English output; "original" (default) keeps the resume's own language.
templateIdstringResume template for the preview page. Defaults to classic-ats.

No output schema declared.

No examples provided.

Common questions

What is the io.github.18boys/matchcv MCP server?

io.github.18boys/matchcv is an MCP server listed in the public MCP registry as io.github.18boys/matchcv. ATS resume checking, job description analysis, and AI resume tailoring powered by MatchCV. This page covers its npm package (matchcv-mcp).

Is the io.github.18boys/matchcv MCP server safe to use?

io.github.18boys/matchcv scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.18boys/matchcv MCP server expose?

io.github.18boys/matchcv exposes 6 tools: ats_check, analyze_job_description, optimize_resume, roast_resume, extract_resume_text, tailor_resume. Their descriptions and schemas cost roughly 674 tokens of context every time the server is loaded.

Is the io.github.18boys/matchcv MCP server still maintained?

io.github.18boys/matchcv is still listed as active in the MCP registry. We last reached this channel on 20 September 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.18boys/matchcv MCP server under?

io.github.18boys/matchcv declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.