Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/smeet666/mcp-ashbyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/smeet666/mcp-ashby/mcp-ashby)<a href="https://agentmods.dev/mcp/smeet666/mcp-ashby/mcp-ashby"><img src="https://agentmods.dev/badge/mcp/smeet666/mcp-ashby/mcp-ashby/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/smeet666/mcp-ashby/mcp-ashby"><img src="https://agentmods.dev/badge/mcp/smeet666/mcp-ashby/mcp-ashby.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-ashby scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"mcp-ashby": {
"command": "npx",
"args": [
"-y",
"mcp-ashby"
],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 10 lines scan A 7281fd6b70de
mcp-ashby is an MCP server published in the GitHub repository smeet666/mcp-ashby (0 stars, last pushed today), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
mcp-lever
Search public Lever job boards: resolve a company, read its openings, read one in full. Runs locally from the mcp-lever npm package.
ats-jobs-mcp
MCP server for open job postings, read first-hand from the applicant-tracking system behind a company's careers page: Greenhouse, Ashby, Lever, Workable. Runs locally from the ats-jobs-mcp Python package.
workway
Search 490k+ live jobs from company ATS boards, save roles, follow companies, manage talent profile. Remote server at www.workway.dev.
jobseek
Search jobs, companies, and watchlists on Job Seek (jseek.co). Runs locally from the @jseek/mcp-server npm package.
swissdevjobs
MCP server "swissdevjobs" as configured in Stupidoodle/swissdevjobs-cli. Runs locally from the git+https://github.com/Stupidoodle/[email protected] Python package. Needs 3 environment variables to run.
openhire
OpenHire 「哨兵」— an MCP job protocol server for AI/Infra, autonomous-driving and embodied-AI roles (US/EU/CN). Résumés never leave your device. Runs locally from the openhire Python package. Needs 1 environment variable to run.