_ registry / mcp http-sse · checked 21m ago

resumeai-ats

https://withresumeai.com

Registry code: 19a17071763da21b

api record

ResumeAI's open ATS data + resume checking server. Use which_ats to find the applicant tracking system a specific large employer uses (portal-verified June 2026 audit, re-verified July 2026), ats_stats for canonical ATS market-share numbers, list_companies to browse the 738-employer dataset, ats_changes for the human-confirmed changelog of employers that switched ATS (living feed; current entries were confirmed by hand, not auto-detected), and check_resume to score a resume 0-100 with per-ATS guidance. get_agent_resume returns a candidate's structured resume (JSON Resume + per-ATS rendering…

endpoint
https://withresumeai.com/api/mcp
protocol
http-sse ·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 it live, free and safe measured by this hub
Is resumeai-ats live?
Yes — it answered the hub's last check (checked 21m ago). It answered 100% of checks over the last 30 days.
Is resumeai-ats free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does resumeai-ats have?
6 tools: check_resume, which_ats, ats_changes, ats_stats, list_companies, get_agent_resume.
Is resumeai-ats 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.
reachable
live
uptime, 30 days
100%

90 days 99.4%· all time 99.4%

latency
238ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 174 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • find which ats an employer uses
  • score a resume for ats compatibility
  • get ats market share statistics
  • list employers by ats vendor
takes → gives
text, documents → data
tools
6 reads
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
3 open1 auth-required 2 never probed 4 of 6 classified

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.

  • ats_changes reads open 21m ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Max changes to return (default 50, the cap)"
        }
      }
    }
    arguments 12 lines
  • ats_stats reads open 21m ago

    Canonical ATS market-share numbers from the October 2026 refresh of ResumeAI's State of ATS 2026 dataset. Workday runs 48.2% of 421 re-verified large employers (October 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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • list_companies reads open 21m ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "ats": {
          "type": "string",
          "maxLength": 100,
          "description": "ATS vendor filter, e.g. 'workday'"
        },
        "industry": {
          "type": "string",
          "maxLength": 100,
          "description": "Industry filter, e.g. 'consulting'"
        },
        "verified_only": {
          "type": "boolean",
          "description": "Only rows confirmed against the live careers portal (default false)"
        }
      }
    }
    arguments 20 lines
  • get_agent_resume reads auth-required 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "token"
      ],
      "properties": {
        "token": {
          "type": "string",
          "maxLength": 256,
          "minLength": 1,
          "description": "The consent token the resume's owner minted and shared, from https://withresumeai.com"
        }
      }
    }
    arguments 15 lines
  • check_resume reads unknown 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "resume_text"
      ],
      "properties": {
        "ats": {
          "type": "string",
          "maxLength": 100,
          "description": "Target ATS vendor, e.g. 'Workday' — adds vendor parsing guidance"
        },
        "api_key": {
          "type": "string",
          "maxLength": 100,
          "description": "Paid API key (ra_live_...) — lifts the 10/day IP cap. Get one at https://withresumeai.com/developers"
        },
        "company": {
          "type": "string",
          "maxLength": 200,
          "description": "Target employer, e.g. 'Nike' — adds its verified ATS + parsing guidance"
        },
        "resume_text": {
          "type": "string",
          "maxLength": 50000,
          "minLength": 100,
          "description": "The resume as plain text"
        },
        "job_description": {
          "type": "string",
          "maxLength": 50000,
          "description": "Job description text — switches scoring to keyword overlap against it"
        }
      }
    }
    arguments 35 lines
  • which_ats reads unknown 14h ago

    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 48.2% of 421 re-verified large employers (October 2026 refresh). The verified sample skews toward vendors with public job APIs. Accepts a company name or slug, e.g. 'Nike' or 'jpmorgan-chase'.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "company"
      ],
      "properties": {
        "company": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Company name or slug, e.g. 'Nike'"
        }
      }
    }
    arguments 15 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 19a17071763da21b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/19a17071763da21b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/19a17071763da21b/badge.svg)](https://brick.blue/agent/19a17071763da21b?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.

_ how we know
card completeness
100%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.