atsprep
Registry code: 5f0eb344d54ca265
ATSPrep checks resumes with fixed, published rules: the same engine as the free tools at atsprep.com. Results are deterministic, so the same text always gets the same answer. Send resume text as plain text with one heading, role or bullet per line. Nothing sent here is stored or logged, and no account is needed. Use check_resume for a score and fixes, match_job to compare with a job posting, check_bullets for single bullets, and open_in_studio to give the user a link that opens their resume in the free editor. Never invent experience to fill a missing keyword. Suggest adding it only where it…
- endpoint
- https://atsprep.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is atsprep live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is atsprep free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does atsprep have?
- 5 tools: open_in_studio, check_bullets, match_job, check_resume, list_templates.
- Is atsprep safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 5 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_templates open 1h ago
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.
{ "type": "object", "properties": {} }arguments 4 linesopen_in_studio unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "resume_text" ], "properties": { "resume_text": { "type": "string", "maxLength": 30000, "description": "The whole resume as plain text, one heading, role or bullet per line." } } }arguments 14 linescheck_bullets unknown 1h ago
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. The same rules and severities as check_resume. Up to 30 bullets of up to 600 characters each; blank items are skipped and reported by index. Rules version 2026-10-18.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "bullets" ], "properties": { "bullets": { "type": "array", "items": { "type": "string", "maxLength": 600 }, "maxItems": 30, "minItems": 1, "description": "One resume bullet per item, at most 30." } } }arguments 19 linesmatch_job unknown never probed
Compare a resume with a job posting: the posting's keywords found in the resume (with how they matched: exact, normalized, alias or stem, and the matched span), the ones missing with the posting sentence they come from, each term's weight and whether the posting lists it as required or preferred, and weighted overall, required and preferred coverage. Posting 120–20,000 characters. Rules version 2026-10-18.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "resume_text", "job_description" ], "properties": { "resume_text": { "type": "string", "maxLength": 30000, "description": "The whole resume as plain text, one heading, role or bullet per line." }, "job_description": { "type": "string", "maxLength": 20000, "minLength": 120, "description": "The full job posting as plain text, including its requirements (120–20,000 characters)." } } }arguments 21 linescheck_resume unknown 1h ago
Score a resume from 0 to 100 with ATSPrep's fixed rules and list each issue with a stable code, where it is and how to fix it. Also reports how the text parsed (roles, experience and project bullets, education, skills and skill groups, input and scored word counts, with definitions). Role-specific advice, such as seniority signals, is given only when the resume names a target title or you pass target_role or job_description; with job_description it also returns a keyword match summary. Resume up to 30,000 characters. Rules version 2026-10-18.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "resume_text" ], "properties": { "resume_text": { "type": "string", "maxLength": 30000, "description": "The whole resume as plain text, one heading, role or bullet per line." }, "target_role": { "type": "string", "maxLength": 120, "description": "Optional. The job title the candidate is applying for." }, "job_description": { "type": "string", "maxLength": 20000, "minLength": 120, "description": "The full job posting as plain text, including its requirements (120–20,000 characters)." } } }arguments 25 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id5f0eb344d54ca265.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/5f0eb344d54ca265/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/5f0eb344d54ca265?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.