Home / MCP registry index / io.github.Devabubakar/atsprep

ATSPrep

io.github.Devabubakar/atsprep in the official MCP registry. Endpoint https://atsprep.com/mcp. Source: github.com/Devabubakar/atsprep-skills.

The registry describes it as: Free resume tools: ATS score, job match, bullet and LinkedIn checks, tailoring, interview prep.

We read its 18 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

check_resume match_job check_bullets open_in_studio list_templates fetch_job_post keyword_scan tailor_resume improve_bullet write_summary action_verbs generate_linkedin_headline check_linkedin_headline check_linkedin_about draft_cover_letter draft_resignation_letter interview_questions review_interview_answer

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-devabubakar-atsprep/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-devabubakar-atsprep)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.