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.

ATS Jobs

PYPI · ATS-JOBS-MCP · 2 COMPONENTS · SCANNED SEP 20

Open jobs read from a company's own careers system: Greenhouse, Ashby, Lever.

+3 this week 83 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 1 of 30 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 561 tokens (~187/item across 3 items; 3 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 Management90
  • Stability observed for 27 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the ATS Jobs MCP server?

ATS Jobs runs locally as a PyPI package, launched with uvx ats-jobs-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · ats-jobs-mcp

# add to Claude Code
claude mcp add groundtruthtools-ats-jobs-mcp -- uvx ats-jobs-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "groundtruthtools-ats-jobs-mcp": {
      "command": "uvx",
      "args": [
        "ats-jobs-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "groundtruthtools-ats-jobs-mcp": {
      "command": "uvx",
      "args": [
        "ats-jobs-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add groundtruthtools-ats-jobs-mcp -- uvx ats-jobs-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "groundtruthtools-ats-jobs-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "ats-jobs-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add groundtruthtools-ats-jobs-mcp --command uvx --arg ats-jobs-mcp
# ~/.hermes/config.yaml
mcp_servers:
  groundtruthtools-ats-jobs-mcp:
    command: "uvx"
    args: ["ats-jobs-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "groundtruthtools-ats-jobs-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "ats-jobs-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add groundtruthtools-ats-jobs-mcp -t stdio -c uvx -a ats-jobs-mcp
// mcp.json
{
  "mcpServers": {
    "groundtruthtools-ats-jobs-mcp": {
      "command": "uvx",
      "args": [
        "ats-jobs-mcp"
      ]
    }
  }
}
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 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1
    • Package version: 1.0.0 → 1.1.0 functional
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

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 20 Sept 2026 · Analysed pypi/ats-jobs-mcp@1.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 30 packages
Packages resolved 30
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~433 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
compare_companies ~115

Open jobs across several companies at once, in one schema. This is the thing no single applicant-tracking system can do: each vendor only knows about its own customers. Companies on different systems come back with the same field names, so they can be compared directly. One company failing does not lose the others; each failure is reported beside the results that did work.

NameTypeReqDescription
companiesarrayyesUp to 20 company board names or careers URLs.
per_companyintegerMaximum postings per company.

No output schema declared.

No examples provided.

find_company_board ~135

Find which applicant-tracking system a company's careers page runs on. Greenhouse, Ashby, Lever and Workable all publish open job board APIs, and all of them are unusable unless you already know the company's board name. None of them publishes a directory of its customers, and none could, since no vendor knows about the others. Use this first when you have a company name rather than a careers URL.

NameTypeReqDescription
companystringyesCompany name or board name, for example 'anthropic' or '1Password'. Case and punctuation do not matter.
limitintegerMaximum matches to return.

No output schema declared.

No examples provided.

list_open_jobs ~183

Every open job at one company, read from its own careers system. Returns title, department, location, employment type, workplace type, posted date, a parsed salary range where the employer publishes one, and a verify_url pointing at the employer's own advert. Salaries are refused rather than guessed: an hourly rate, an ambiguous currency, or bands in two currencies all yield no figure, and salary_text keeps whatever the employer actually wrote.

NameTypeReqDescription
companystringyesA company's board name ('stripe'), a careers URL ('https://jobs.ashbyhq.com/ramp'), or system:name ('ashby:ramp').
include_descriptionbooleanInclude the full job description. Off by default because descriptions are long; email addresses and phone numbers are removed from them either way.
limitintegerMaximum postings to return.

No output schema declared.

No examples provided.

Common questions

What is the ATS Jobs MCP server?

ATS Jobs is an MCP server listed in the public MCP registry as io.github.groundtruthtools/ats-jobs-mcp. Open jobs read from a company's own careers system: Greenhouse, Ashby, Lever. This page covers its PyPI package (ats-jobs-mcp).

Is the ATS Jobs MCP server safe to use?

ATS Jobs scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 ATS Jobs MCP server expose?

ATS Jobs exposes 3 tools: find_company_board, list_open_jobs, compare_companies. Their descriptions and schemas cost roughly 433 tokens of context every time the server is loaded.

Is the ATS Jobs MCP server still maintained?

ATS Jobs is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the ATS Jobs MCP server under?

ATS Jobs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.