
Official MCP RegistryListed
ATSPrep
Free resume tools: ATS score, job match, bullet and LinkedIn checks, tailoring, interview prep.
First seen 18 Oct 2026. Evidence as of 17 Nov 2026.
19
Tools
From an anonymous probe
1
Source listings
Each with its own history
50
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| action_verbs | Use this when the user wants stronger verbs or synonyms for resume wording. Suggest resume action verbs. Pass a weak opener ("responsible for", "helped") for direct swaps and why they read weak, or the work in plain words ("trained new staff", "cut costs") for the matching verb groups with an example bullet. Leave query empty for every group. | Read-only |
| check_bullets | Use this when the user wants a few resume bullet points checked without sending the whole resume. Give each resume bullet a score, a verdict and specific fixes with stable codes: weak openers, missing scale or result, numbers that show neither, hard-to-believe claims, first person, vague claims. Scored as check_resume scores bullets, with the same severities. Up to 30 bullets of up to 600 characters each; blank items are skipped and reported by index. Rules version 2026-11-11.1. | Read-only |
| check_linkedin_about | Use this when the user wants their LinkedIn About or summary section reviewed. Check a LinkedIn About section: what shows before "see more" on a phone and on a computer, whether the opening says who they are, results with numbers, buzzwords, a clear next step, and the 2,600-character limit. | Read-only |
| check_linkedin_headline | Use this when the user wants their existing LinkedIn headline reviewed. Check a LinkedIn headline: length against the 220-character limit, what shows in search results before the cut, whether it leads with a searchable job title, and buzzwords or vague claims to replace. | Read-only |
| check_resume | Use this when the user shares a resume (pasted text or a file's text) and wants it checked, scored, reviewed for ATS problems, or wants to know what to fix. The headline score is resumeQuality (0 to 100), the same resume-quality metric as Studio; score is its compatibility alias. Adding job_description never replaces it with job fit. jobFit (requirements, evidence and readability, with caps) and keywordCoverage are returned separately alongside the legacy job_fit breakdown and job_match summary; never average these metrics. An AI line judge labels bullets against the published rubric; fixed maths and rules make the score, with versioned rules fallback when unavailable. Lists issues with stable codes, locations and fixes, plus import counts and definitions. target_role or job_description can refine advice without changing the quality headline. Pass language when the resume isn't in English. Resume up to 30,000 characters. Rules version 2026-11-11.1. | Read-only |
| draft_cover_letter | Use this when the user wants a cover letter for a job. Draft a cover letter from the user's resume and the job posting with fixed rules: name, contact details and up to two results from the resume, the job title and top keywords from the posting. Facts that are missing show as [square-bracket] gaps for the user to fill, never as stand-ins. Returns the letter, the gaps and a checklist. | Read-only |
| draft_resignation_letter | Use this when the user wants to resign and needs a resignation letter or their last working day. Draft a short, professional resignation letter and work out the last working day from the notice period. Missing facts show as [square-bracket] gaps. Returns the letter, the last day and a checklist (notice stated, no complaints, length). | Read-only |
| fetch_job_post | Use this when the user gives a job posting link instead of its text; then pass the result to the job tools. Read a public job posting from its link and return the title, company, location and full description as plain text, ready for match_job, tailor_resume, keyword_scan or interview_questions. Reads LinkedIn, Greenhouse, Lever, Ashby, SmartRecruiters, Workable, Workday and most company careers pages. Some sites block reading; then ask the user to paste the text. With questions: true it also returns the application form's questions where the site publishes them; eeo, legal, consent, ai-use and trap questions are the user's to answer. | Read-only |
| generate_linkedin_headline | Use this when the user wants new LinkedIn headline ideas. Write LinkedIn headline options from the user's answers, each in a proven pattern (title and focus, title and result, title and who you help…), with its length and roughly what shows in search before the cut. Uses only the answers given. | Read-only |
| improve_bullet | Use this when the user wants one resume bullet rewritten or made stronger. Check one resume bullet as check_bullets does (score, verdict, fixes) and suggest up to three stronger rewrites that keep every fact as given. ask_user names the one fact to ask the user for; never invent it. Part of the answer is drafted by an AI model (Gemma 4, with Llama 3.3 70B as a backup, on Cloudflare Workers AI) behind ATSPrep's guard, which drops any figure, name or tool the user's text doesn't contain. If the AI part is unavailable, the rule-based part still comes back and ai.message says why. | Read-only |
| interview_questions | Use this when the user is preparing for an interview and wants likely questions, for a specific job or in general. Interview questions to practise, each with what the interviewer is listening for, plus STAR answer tips. With a job_description, questions come from its skills and duties, along with what to research and questions to ask; with resume_text, from the user's own roles. Rule-based. | Read-only |
| keyword_scan | Use this when the user has only a job posting (no resume yet) and wants its key skills and keywords. List the skills, tools and requirements a job posting asks for, ranked by how hard it leans on each (repetition, position, required or preferred headings), with the high-priority ones flagged. Use match_job to see which a resume already shows. Posting 120–20,000 characters. Rules version 2026-11-11.1. | Read-only |
| list_templates | Use this when the user asks for resume templates, designs or example resumes for a role. List ATSPrep's resume designs, each with a link that opens Studio in that design, and the example resumes by role, each with a link that opens it in Studio and a preview image. | Read-only |
| match_job | Use this when the user has a resume and a job posting and asks how well they match, what keywords are missing, or whether to apply. For rewrites, use tailor_resume instead. Returns the Studio's resumeQuality as the headline, jobFit separately, and keywordCoverage (also coverage for compatibility). Never average them. Lists matched and missing terms, their posting sentences, match types, weights and required/preferred coverage. Quality uses the versioned judge with rules fallback; keyword coverage uses fixed rules. Posting 120–20,000 characters. Rules version 2026-11-11.1. | Read-only |
| open_in_studio | Use this when the user wants to edit their resume in an editor, apply a template, or download it as a PDF or Word file. Make a link that opens this resume in ATSPrep Studio, the free editor, so the user can fix it, pick a template and download a PDF. The text travels in the link's #fragment, which is never sent to a server. | Read-only |
| review_interview_answer | Use this when the user gives an answer to an interview question and wants feedback on it. Review the user's answer to an interview question: a rating, length and speaking time, STAR coverage for stories, filler words, specific checks, the follow-up an interviewer would likely ask, and a stronger version that keeps to the user's own facts. Part of the answer is drafted by an AI model (Gemma 4, with Llama 3.3 70B as a backup, on Cloudflare Workers AI) behind ATSPrep's guard, which drops any figure, name or tool the user's text doesn't contain. If the AI part is unavailable, the rule-based part still comes back and ai.message says why. | Read-only |
| suggest_roles | Use this when the user asks what jobs or roles they could apply for, or what their resume fits. Read the resume against what postings for each of 60 roles (office, health, retail, hospitality, trades, tech, sales, design and more) usually ask for, phrased as postings in Kenya, the Gulf, India, the UK and the US put it, and return up to 3 roles: how many of those asks the resume shows (a count, never a percent), its strongest ones, the first gaps, whether it matches their own job title, and search links for openings near them. These are typical asks, not a real posting: then ask the user for a real opening and run match_job or tailor_resume on it. Never tailor a resume to the typical asks. | Read-only |
| tailor_resume | Use this when the user wants their resume rewritten or tailored for a specific job posting. Returns the original resume's resumeQuality as the headline, with jobFit and keywordCoverage separately; never average them or claim suggested edits are already applied. Lists missing posting terms and suggested rewrites that preserve facts and ownership; a probable qualitative outcome is a suggestion to keep only if true. Never invent exact figures, names or tools. Each edit lists borrowed posting terms; confirm_with_user lists terms to confirm before adding. End with next_step, the link to check edits and download in ATSPrep. Part of the answer is drafted by an AI model (Gemma 4, with Llama 3.3 70B as a backup, on Cloudflare Workers AI) behind ATSPrep's guard, which drops any figure, name or tool the user's text doesn't contain. If the AI part is unavailable, the rule-based part still comes back and ai.message says why. | Read-only |
| write_summary | Use this when the user wants a resume summary or professional profile written from their resume. Draft professional summaries from a resume: rule-based drafts built from its title, skills and the bullets that carry a figure, plus AI drafts that use only facts in the resume. Part of the answer is drafted by an AI model (Gemma 4, with Llama 3.3 70B as a backup, on Cloudflare Workers AI) behind ATSPrep's guard, which drops any figure, name or tool the user's text doesn't contain. If the AI part is unavailable, the rule-based part still comes back and ai.message says why. | Read-only |
Change history
- match_job: description changed (+"2026-11-11.1." -"2026-11-05.2.")
- keyword_scan: description changed (+"2026-11-11.1." -"2026-11-05.2.")
- check_resume: description changed (+"2026-11-11.1." -"2026-11-05.2.")
- check_bullets: description changed (+"2026-11-11.1." -"2026-11-05.2.")
- tailor_resume: description changed (+"Returns" +"original resume's resumeQuality as" +"headline, with jobFit and keywordCoverage separately; never average them or claim suggested edits are already applied. Lists")
- match_job: description changed (+"Returns" +"Studio's resumeQuality as" +"headline, jobFit separately,")
- keyword_scan: description changed (+"2026-11-05.2." -"2026-10-31.1.")
- check_resume: description changed (+"The headline score is resumeQuality (0" +"100), the same resume-quality metric" +"Studio; score is its compatibility alias. Adding job_description never replaces it with job fit. jobFit (requirements, evidence and readability, with caps) and keywordCoverage are returned separately alongside the legacy job_fit breakdown and job_match summary; never average these metrics. An")
- check_bullets: description changed (+"2026-11-05.2." -"2026-10-31.1.")
- server instructions changed (+"exact figures, tools" +"employers. A resume suggestion may add a probable qualitative outcome: the user keeps it only if true. The first suggestion is finished wording;" +"single editable number blank such as [X%] belongs only in an optional alternative, never an automatically applied fix. A")
- improve_bullet: description changed (+"as check_bullets does" -"with the fixed rules")
- fetch_job_post: input schema changed (+questions)
- fetch_job_post: description changed (+"With questions: true it also returns the application form's questions where the site publishes them; eeo, legal, consent, ai-use and trap questions are the user's to answer.")
- check_resume: description changed (+"as atsprep.com does (an AI line judge labels each bullet against the published rubric;" +"maths and" +"make the score)")
- check_bullets: description changed (+"Scored as check_resume scores bullets, with the" +"severities." -"The")
- server instructions changed (+"check_resume, check_bullets and improve_bullet's check score each bullet the way atsprep.com does: an AI line judge (Claude, Anthropic) gives it four labels from a published rubric (what changed, scale, specifics, believable), and fixed maths and rules turn the labels" +"the page's" +"into the score. A judged line is kept by its words, so the same text gets the same score; scored_by says whether the judge or the rules alone scored it, and when the judge is unavailable the rules do.")
- match_job: description changed (+"2026-10-31.1." -"2026-10-30.1.")
- keyword_scan: description changed (+"2026-10-31.1." -"2026-10-30.1.")
- check_resume: description changed (+"2026-10-31.1." -"2026-10-30.1.")
- check_bullets: description changed (+"2026-10-31.1." -"2026-10-30.1.")
- suggest_roles: description changed (+"60" -"35")
- match_job: description changed (+"2026-10-30.1." -"2026-10-29.1.")
- keyword_scan: description changed (+"2026-10-30.1." -"2026-10-29.1.")
- check_resume: description changed (+"2026-10-30.1." -"2026-10-29.1.")
- check_bullets: description changed (+"2026-10-30.1." -"2026-10-29.1.")
- match_job: description changed (+"2026-10-29.1." -"2026-10-28.1.")
- keyword_scan: description changed (+"2026-10-29.1." -"2026-10-28.1.")
- check_resume: description changed (+"2026-10-29.1." -"2026-10-28.1.")
- check_bullets: description changed (+"2026-10-29.1." -"2026-10-28.1.")
- match_job: description changed (+"2026-10-28.1." -"2026-10-26.3.")
- keyword_scan: description changed (+"2026-10-28.1." -"2026-10-26.3.")
- check_resume: description changed (+"2026-10-28.1." -"2026-10-26.3.")
- check_bullets: description changed (+"2026-10-28.1." -"2026-10-26.3.")
- match_job: description changed (+"2026-10-26.3." -"2026-10-25.4.")
- keyword_scan: description changed (+"2026-10-26.3." -"2026-10-25.4.")
- check_resume: description changed (+"2026-10-26.3." -"2026-10-25.4.")
- check_bullets: description changed (+"2026-10-26.3." -"2026-10-25.4.")
- match_job: description changed (+"2026-10-25.4." -"2026-10-25.1.")
- keyword_scan: description changed (+"2026-10-25.4." -"2026-10-25.1.")
- check_resume: input schema changed (+language)
- check_resume: description changed (+"Pass language when the resume isn't in English." +"2026-10-25.4." -"2026-10-25.1.")
- check_bullets: input schema changed (+language)
- check_bullets: description changed (+"2026-10-25.4." -"2026-10-25.1.")
- suggest_roles: tool added
- match_job: description changed (+"2026-10-25.1." -"2026-10-23.5.")
- keyword_scan: description changed (+"2026-10-25.1." -"2026-10-23.5.")
- check_resume: description changed (+"2026-10-25.1." -"2026-10-23.5.")
- check_bullets: description changed (+"2026-10-25.1." -"2026-10-23.5.")
- server instructions changed (+"When" +"wants" +"PDF, call open_in_studio with their resume text and give them its link: it opens their resume in ATSPrep with the same score and fixes. Other tools' open_in_atsprep links open that tool's page, without the resume.")
- match_job: description changed (+"2026-10-23.5." -"2026-10-21.1.")
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | io.github.Devabubakar/atsprep | 18 Oct 2026 | 17 Nov 2026 | 1 |