ATS Engine
NPM · @VERIWORKLY/ATS-ENGINE-MCP
Read your own resume the way an ATS does and score it with a published, deterministic rubric.
Available components
Last scanned (3 hours ago)
Scores higher than 95% of npm servers
Category Testing and QA
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
- 45 of 142 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to VeriWorkly/ats-engine). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1425 tokens (~285/item across 5 items; 4 tools + 1 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 Management77
- Stability observed for 23 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.15.0 → 0.15.1 functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
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 5 Nov 2026 · Analysed npm/@veriworkly/ats-engine-mcp@0.15.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | VeriWorkly/ats-engine |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/VeriWorkly/ats-engine/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3537979812 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:37e01675fd66fcdbe96e15ccc600c4c41615ca63133ccc64cc313424f4ca72f3fa25ff73369e65368edf1097ad497668b672f2e86596ade2c079297eb |
Background: How many MCP packages publish verified provenance →
Dependencies 142 packages
| Packages resolved | 142 |
|---|---|
| Stale | 45 |
| 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 →
check_resume Check my resume ~494
Reads the user's resume the way an applicant tracking system (ATS) does and scores it: readiness score (0-100), verdict, per-category scores, every failed check with its evidence and fix, and the fields an ATS would store (name, contact, roles, education, skills). With a job posting it adds the job match score and each requirement judged. Advice that is not scored (the file, age signals, a named ATS's documented notes) comes apart from the score. The score comes from a published, deterministic rubric (the same file gets the same score from the same engine on the same day), not from an AI model; present it as the rubric's result, not your own judgement. Use it only on the user's own resume, at their request: it is a tool for candidates. Never use it to screen, rank, compare or reject other people. Runs locally and reads only the files named in the call; nothing is sent anywhere.
| Name | Type | Req | Description |
|---|---|---|---|
| job_path | string | – | Path to a job posting: .txt, .md, .pdf, .docx, or a saved .html page. Optional; give job_path or job_text. |
| job_text | string | – | The job posting as text. Optional; give job_path or job_text, not both. |
| language | string | – | Read the resume and the posting in this language (en, de, fr, hi, es, pt; en: English only). Default: detected from each. Give it only when the resume was read in the wrong language; a posting in ano… |
| path | string | – | Absolute path to the user's resume: .pdf, .docx, .html, .txt, .md, or a .json JSON Resume or ats-resume document. Give path or text, not both. |
| region | string | – | Read the resume as from this country (US, DE, FR, GB, IN, ES, BR, PT, MX, AR, CO, CL). Default: inferred from it. |
| target_ats | string | – | The applicant tracking system the user is applying through (greenhouse, lever, taleo), to add its vendor's documented notes, each with its source. Advice only; never scored. |
| text | string | – | The resume as plain text, when there is no file. Give path or text, not both. |
| Name | Type | Req | Description |
|---|---|---|---|
| advice | array | yes | Not scored: the file (name, size, password, tracked changes), details that can invite age bias where the region calls for it, and a named ATS's documented notes. |
| categories | array | yes | – |
| checksPassed | number | yes | – |
| checksTotal | number | yes | – |
| engine | object | yes | – |
| failedChecks | array | yes | Every failed check, with its evidence and fix. |
| job | – | yes | The match against the posting; null when no posting was given. |
| locale | object | yes | – |
| parsed | object | yes | The fields an ATS would store from this resume. |
| parsingWarnings | array | yes | – |
| prioritizedFixes | array | yes | – |
| readinessScore | number | yes | 0-100, how well an ATS reads and ranks the resume. |
| strengths | array | yes | – |
| verdict | string | yes | – |
| wordCount | number | yes | – |
No examples provided.
explain_rule Explain a rubric rule ~141
Explains one rule of the published rubric by its id (as in a failed check's id): its category, severity, what it checks, how many points it is worth, and how to fix it. With a region, as that country weighs it. The full rubric is the resource rubric://default.
| Name | Type | Req | Description |
|---|---|---|---|
| region | string | – | The country the resume was scored as (US, DE, FR, GB, IN, ES, BR, PT, MX, AR, CO, CL), as in a report's locale. Default: none, the published weights. |
| rule_id | string | yes | A rule id, e.g. from failedChecks. |
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| deduction | boolean | yes | – |
| fix | string | yes | – |
| id | string | yes | – |
| measures | string | yes | – |
| passes | string | yes | – |
| points | number | yes | – |
| severity | string | yes | – |
No examples provided.
extract_text Show my resume as an ATS reads it ~236
The user's resume text in the order an ATS reads it, line by line — after columns are untangled and wrapped lines rejoined — with what the layout measured (columns, tables, hidden text) and the parsing warnings. For answering 'why did it read my resume like this?'. Use it only on the user's own resume, at their request: it is a tool for candidates. Never use it to screen, rank, compare or reject other people. Runs locally and reads only the files named in the call; nothing is sent anywhere.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Absolute path to the user's resume: .pdf, .docx, .html, .txt, .md, or a .json JSON Resume or ats-resume document. Give path or text, not both. |
| region | string | – | Read the resume as from this country (US, DE, FR, GB, IN, ES, BR, PT, MX, AR, CO, CL). Default: inferred from it. |
| text | string | – | The resume as plain text, when there is no file. Give path or text, not both. |
| Name | Type | Req | Description |
|---|---|---|---|
| layout | – | yes | What the file's layout measured (columns, tables, hidden text); null for text. |
| lines | array | yes | The text in the order an ATS reads it. At most 500 lines. |
| parsingWarnings | array | yes | – |
| wordCount | number | yes | – |
No examples provided.
match_job Match my resume to a job ~397
Matches the user's resume against one job posting: the job match score (0-100), each requirement of the posting judged met, partial, missing or unverifiable with the resume's own words as evidence, and the posting's keywords the resume lacks. The score comes from a published, deterministic rubric (the same file gets the same score from the same engine on the same day), not from an AI model; present it as the rubric's result, not your own judgement. Use it only on the user's own resume, at their request: it is a tool for candidates. Never use it to screen, rank, compare or reject other people. Runs locally and reads only the files named in the call; nothing is sent anywhere.
| Name | Type | Req | Description |
|---|---|---|---|
| job_path | string | – | Path to a job posting: .txt, .md, .pdf, .docx, or a saved .html page. Give job_path or job_text. |
| job_text | string | – | The job posting as text. Give job_path or job_text, not both. |
| language | string | – | Read the resume and the posting in this language (en, de, fr, hi, es, pt; en: English only). Default: detected from each. Give it only when the resume was read in the wrong language; a posting in ano… |
| path | string | – | Absolute path to the user's resume: .pdf, .docx, .html, .txt, .md, or a .json JSON Resume or ats-resume document. Give path or text, not both. |
| region | string | – | Read the resume as from this country (US, DE, FR, GB, IN, ES, BR, PT, MX, AR, CO, CL). Default: inferred from it. |
| text | string | – | The resume as plain text, when there is no file. Give path or text, not both. |
| Name | Type | Req | Description |
|---|---|---|---|
| jobMatchScore | number|null | yes | 0-100, how well the resume meets the posting. |
| missingKeywordGroups | object | yes | The same terms by kind; soft skills weigh less in the match. |
| missingKeywords | array | yes | – |
| requirements | array | yes | Each requirement of the posting, judged. |
No examples provided.
How do I install the ATS Engine MCP server?
ATS Engine runs locally as an npm package, launched with npx -y @veriworkly/ats-engine-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 · @veriworkly/ats-engine-mcp
claude mcp add veriworkly-ats-engine -- npx -y @veriworkly/ats-engine-mcp
What is the ATS Engine MCP server?
ATS Engine is an MCP server listed in the public MCP registry as io.github.VeriWorkly/ats-engine. Read your own resume the way an ATS does and score it with a published, deterministic rubric. This page covers its npm package (@veriworkly/ats-engine-mcp).
Is the ATS Engine MCP server safe to use?
ATS Engine scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 ATS Engine MCP server expose?
ATS Engine exposes 4 tools: check_resume, match_job, explain_rule, extract_text. Their descriptions and schemas cost roughly 1,268 tokens of context every time the server is loaded.
Is the ATS Engine MCP server still maintained?
ATS Engine is still listed as active in the MCP registry. We last reached this channel on 5 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 ATS Engine MCP server under?
ATS Engine declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.