VerbatimCV-mcp
OfficialRelated Servers
Alternatives to VerbatimCV-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceDeterministic MCP server for job-landing pipeline that parses CVs into validated JSON Resume, detects sections, scores parse confidence, and exposes FR/US market profiles to help beat ATS and LLM screeners honestly.75MIT
- AlicenseAqualityDmaintenanceMCP server that simulates how 5 real ATS parsers (Workday, Greenhouse, Lever, Taleo, iCIMS) read a CV. Pure JS lint engine, MIT licensed, no network calls in lint logic. Vendor-specific rules cite their public sources.3MIT
- FlicenseNot gradedqualityDmaintenanceThis server enables remote job discovery, tailored CV creation, and approval-gated application lifecycle management. It prioritizes safe, factual job applications without authenticated LinkedIn scraping or silent submissions.-
- AlicenseAqualityBmaintenanceAuto-Apply That Ends on an Interview. Job matches, applications submitted on the employer's own hiring system automatically or after your approval, employer-receipt tracking, a resume rewritten for each role, cover letters and interview prep. Hosted remote server over Streamable HTTP with OAuth 2.1.412,047 npm4MIT
- AlicenseAqualityBmaintenanceServes CV content in Markdown, PDF, LaTeX, HTML, and Typst formats, with semantic querying and tailored CV rendering capabilities.16MIT
- AlicenseAqualityDmaintenanceOfficial MCP server for FormaCV, enabling AI-powered CV formatting, anonymization, tailoring, and ATS push-back from AI agents like Claude Desktop and Cursor.836 npm18MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong tool or confusing overlapping purposes. Its purpose is clearly scoped to parsing a single CV/resume.
The single tool name `parse_resume` follows a clear verb_noun convention. There are no competing naming styles to create inconsistency.
A single tool is reasonable for a narrowly focused resume-parsing server, and it appears to encapsulate the full extraction workflow. It is slightly thin compared with multi-tool servers, but not mismatched to the stated purpose.
The tool covers the core resume-parsing lifecycle: input via file or URL, structured extraction, safety handling, warnings, and agent guidance. Minor gaps could include batch parsing or a separate schema/version lookup, but the main domain operation is present.