Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.withresumeai/ats

REMOTE · WITHRESUMEAI.COM

Which ATS does a company use? Portal-verified answers for 743 employers + resume ATS check. No key.

Available components

−9 this week 77 Trust /100

Last scanned (22 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1126 tokens (~187/item across 6 items; 6 tools + 0 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 Management33
  • Stability observed for 10 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 −9
    • Stability: pass → 0.30 functional
  • 11 Nov 26 +63
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • HSTS header: fail → pass ▲ security
    • Transport: fail → pass ▲ security
    • Tool “ats_stats” rewrote its description, which is the text the model reads security
    • Tool “which_ats” rewrote its description, which is the text the model reads security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 21 Oct 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • HSTS header: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 10 Oct 26 0
    • Tool “ats_stats” rewrote its description, which is the text the model reads security
    • Tool “which_ats” rewrote its description, which is the text the model reads security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 2026 · Probed https://withresumeai.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.withresumeai.com CN=YR1,O=Let's Encrypt,C=US 17 Nov 2026 15 Feb 2027 RSA 2048 SHA256-RSA 5a33df61783ec2ba6bd718ac2104d6ddce3
SANs: *.withresumeai.com, withresumeai.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of withresumeai.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
withresumeai.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy frame-ancestors 'self'; base-uri 'self'; form-action 'self' https://*.stripe.com;
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://withresumeai.com/api/mcp Verified 200
http (plaintext) http://withresumeai.com/api/mcp HTTPS enforced 308 https://withresumeai.com/api/mcp
MCP tools · 6 exposed · ~937 tokens

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 →

Tool Tokens
ats_changes ~150

The living-feed counterpart of the dataset: which tracked employers changed their applicant tracking system. Every entry currently in the feed was confirmed by a person against the live careers portal during the July 2026 re-verification and published together, which is why they share a timestamp — the automated sweep has not yet detected one on its own. Employers whose vendor exposes a probeable board or tenant host are re-probed on a rolling sweep, and a suspected change is human-confirmed before it appears here. An empty list means no confirmed changes yet, not that monitoring is off. Returns at most 50 rows, newest first.

NameTypeReqDescription
limitinteger–Max changes to return (default 50, the cap)

No output schema declared.

No examples provided.

ats_stats ~90

Canonical ATS market-share numbers from the November 2026 refresh of ResumeAI's State of ATS 2026 dataset. Workday runs 47.5% of 436 re-verified large employers (November 2026 refresh). The verified sample skews toward vendors with public job APIs. Every share in the response is computed from that re-verified subset, so quote those rather than this summary.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

check_resume ~243

Score a resume 0-100 with ResumeAI's production ATS engine — the same one behind https://withresumeai.com/ats-checker. Returns a breakdown (keywords, format, sections, content, length), concrete fixes, and missing keywords. Optionally pass a target company (to get that employer's verified ATS + vendor-specific parsing rules) and/or a job description (to score keyword overlap against the posting). Rate limited to 10 checks per day per IP; pass a paid api_key ($49/mo at https://withresumeai.com/developers) for unlimited calls.

NameTypeReqDescription
api_keystring–Paid API key (ra_live_...) — lifts the 10/day IP cap. Get one at https://withresumeai.com/developers
atsstring–Target ATS vendor, e.g. 'Workday' — adds vendor parsing guidance
companystring–Target employer, e.g. 'Nike' — adds its verified ATS + parsing guidance
job_descriptionstring–Job description text — switches scoring to keyword overlap against it
resume_textstringyesThe resume as plain text

No output schema declared.

No examples provided.

get_agent_resume ~189

Fetch a job seeker's structured, machine-readable resume as JSON Resume (https://jsonresume.org/schema/) — but ONLY when its human owner has explicitly shared a consent token for it. Pass that token and the tool returns the JSON Resume plus ats_context: how to render the profile for the owner's target applicant tracking system, grounded in ResumeAI's portal-verified State of ATS 2026 data (recommended file format, layout, and vendor parsing rules). No token, an invalid token, or a token the owner has revoked returns nothing. There is no way to browse, search, list, or enumerate resumes with this server — the owner-minted token is the only key, and the owner can revoke it at any time. This tool never exposes personal data without one.

NameTypeReqDescription
tokenstringyesThe consent token the resume's owner minted and shared, from https://withresumeai.com

No output schema declared.

No examples provided.

list_companies ~144

List employers from the State of ATS 2026 dataset, optionally filtered by ATS vendor (case-insensitive substring, e.g. 'workday', 'greenhouse', 'oracle') and/or industry (substring, e.g. 'health', 'consulting'). Returns at most 100 rows per call — narrow the filters or fetch the full dataset from https://withresumeai.com/api/v1/ats.

NameTypeReqDescription
atsstring–ATS vendor filter, e.g. 'workday'
industrystring–Industry filter, e.g. 'consulting'
verified_onlyboolean–Only rows confirmed against the live careers portal (default false)

No output schema declared.

No examples provided.

which_ats ~121

Look up the applicant tracking system (ATS) a specific large employer uses, from ResumeAI's State of ATS 2026 dataset (738 Fortune 500 / Global 2000 employers). Workday runs 47.5% of 436 re-verified large employers (November 2026 refresh). The verified sample skews toward vendors with public job APIs. Accepts a company name or slug, e.g. 'Nike' or 'jpmorgan-chase'.

NameTypeReqDescription
companystringyesCompany name or slug, e.g. 'Nike'

No output schema declared.

No examples provided.

Install

How do I install the com.withresumeai/ats MCP server?

com.withresumeai/ats is a hosted endpoint at https://withresumeai.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · withresumeai.com

# add to Claude Code
claude mcp add --transport http com-withresumeai-ats 'https://withresumeai.com/api/mcp'
Common questions

What is the com.withresumeai/ats MCP server?

com.withresumeai/ats is an MCP server listed in the public MCP registry as com.withresumeai/ats. Which ATS does a company use? Portal-verified answers for 743 employers + resume ATS check. No key. This page covers its hosted endpoint (https://withresumeai.com/api/mcp).

Is the com.withresumeai/ats MCP server safe to use?

com.withresumeai/ats scores 77 out of 100 on VerifyMCP. 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 com.withresumeai/ats MCP server expose?

com.withresumeai/ats exposes 6 tools: which_ats, ats_stats, list_companies, ats_changes, check_resume, get_agent_resume. Their descriptions and schemas cost roughly 937 tokens of context every time the server is loaded.

Does the com.withresumeai/ats MCP server require authentication?

No. We connected to com.withresumeai/ats without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.withresumeai/ats MCP server still maintained?

com.withresumeai/ats is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the com.withresumeai/ats MCP server?

VerifyMCP ran 13 checks on com.withresumeai/ats, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.