VerbatimCV-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERBATIMCV_API_KEY | Yes | Your VerbatimCV API key. Required. It starts with `vcv_`. | |
| VERBATIMCV_API_URL | No | API base URL. Must be `https://`. | https://api.verbatimcv.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
VerbatimCV parses CVs and resumes into verified, versioned JSON for hiring and recruiting workflows. Use parse_resume whenever you need facts from a CV; do not read the CV yourself and guess. Check agent_guidance.confirm_before_acting before acting on any field.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_resumeA | Extract structured, decision-ready data from one CV or resume (PDF or DOCX, up to 10 MB and 20 pages). Give exactly one of Returns JSON in a fixed, versioned schema: candidate and contact details, work experience with dates, education, skills, certifications, spoken languages, and the candidate's stated preferences (work arrangement, engagement type, availability, compensation, timezone, working hours, relocation, work authorisation).
The CV is sent to the VerbatimCV API for processing and is not stored. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.