io.github.gzchenhao/openhire
Provides job search, watch intents, and application authorization for job listings sourced from employers' Greenhouse ATS APIs.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@io.github.gzchenhao/openhireFind me remote jobs for AI engineers with Rust and Kubernetes skills."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
openhire-mcp
Jobs come to you. Your résumé never passes through OpenHire's servers, and we never store it. 岗位来找你,简历不经过我们的服务器,也不被我们存储。
An MCP server that turns your AI assistant (Claude, Cursor, Windsurf) into a private radar for AI / Infra, autonomous-driving and embodied-AI roles — sourced directly from ~120 company career sites and their public ATS APIs (Greenhouse / Lever / Ashby / 北森 Beisen), in the US, Europe and China. No account. No signup. No résumé upload. Ever.
Matching runs on your machine; only an anonymous fingerprint and hard filters ever reach the
server. This is the 「哨兵 / Sentinel」 reference implementation — see
design_handoff_openhire_v01/README.md for the full protocol spec.
Quickstart — under a minute
# 1. Install (pipx keeps it isolated and puts `ohp` on your PATH)
pipx install openhire
# 2. Get a job index. Default: download the public snapshot, then refresh it live.
ohp bootstrap
# --fresh crawl the public ATS from scratch (heuristic, free, no snapshot)
# --deepseek higher-quality extraction using YOUR OWN DEEPSEEK_API_KEY
# 3. Use it directly…
ohp search --required-skills rust,k8s --remote --role-family engineering
# …or connect it to an MCP client:
ohp serveThen point your MCP client at it — see Works with below.
Related MCP server: jobjourney-claude-plugin
Works with
All clients use the same MCP entry. If you ran pipx install openhire, use ohp; otherwise
uvx openhire serve fetches and runs it with no prior install (needs uv).
Claude Desktop — %APPDATA%\Claude\claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/); quit & reopen after editing:
{ "mcpServers": { "openhire": { "command": "ohp", "args": ["serve"] } } }Cursor — ~/.cursor/mcp.json (or a project .cursor/mcp.json):
{ "mcpServers": { "openhire": { "command": "uvx", "args": ["openhire", "serve"] } } }Windsurf — ~/.codeium/windsurf/mcp_config.json:
{ "mcpServers": { "openhire": { "command": "uvx", "args": ["openhire", "serve"] } } }Run
ohp bootstraponce first so the index has data. On Windows Claude Desktop from the Microsoft Store, the config is under…\Packages\<Claude package>\LocalCache\Roaming\Claude\.
What it does
Tool | What it gives you |
| Hard-filter the live index; every result carries |
| Register a standing intent once — new matching jobs are waiting next time you check, even after you close the terminal. Accepts |
| Pull the matches that are new since your last check (client-pull; stdio has no push). |
| One explicit confirmation per job. It records your authorization and returns the employer's own application URL — you apply as yourself. It cannot accept a résumé. |
| Aggregate, anonymous trust signals for one employer ( |
Optional, entirely local: ohp init --scan <dir> derives a skill fingerprint from your
own repos. You never write a résumé; the code never leaves your machine — only an anonymous
vector does.
The five protocol fields
Every listing is valid schema.org/JobPosting, plus:
verified_at— last moment confirmed live on the employer's own sitesource—employer_site | ats_public_api(never a job board)ghost_score— 0–1 likelihood the listing is not a real, active hire (ages off the real posting date; lower is better)response_sla_days— employer's committed response window (v0.1: always null)apply_channel— always the employer's own application URL, deep-linked to the specific job
Privacy model
Résumé / PII upload | never — matching runs locally; a résumé never transits the server, and we never store one |
What the server sees | one anonymous, client-generated fingerprint + hard filters |
Repo scan | local-only · personal projects · explicit consent · opt-out anytime |
Job sources | first-party only: employer career pages + public ATS APIs (Greenhouse / Lever / Ashby) |
First-run data — the snapshot vs. fresh
ohp bootstrap (default) downloads a small public index snapshot (a GitHub Release
asset — companies + jobs only, zero user data) and then runs one incremental crawl to
refresh verified_at / delisting. --fresh skips the snapshot and crawls the public ATS from
scratch with the free offline heuristic extractor. Either way: no account, no PII.
Three rules this project will never break
Your résumé stays on your machine — it never transits the server, and we never store it.
Ranking is not for sale — it is only
f(match_quality, freshness), a locked pure function.Employers pay only for authorized, delivered outcomes — never for exposure. (v0.1 has no billing at all.)
These are enforced by CI (tests/test_privacy.py, tests/test_ranking.py,
tests/test_snapshot.py).
Development
python -m venv .venv && . .venv/Scripts/activate # Windows
pip install -e ".[dev]"
pytest # privacy red lines + ranking + snapshot must be greenSet OPENHIRE_DATABASE_URL=postgresql+psycopg://… to run against Postgres instead of the
default local SQLite file (~/.openhire/openhire.db).
Roadmap
v0.2 — CN ATS adapters (Beisen / Moka) ·
ghost_scorepublic betav0.3 — Employer claim + verified badges · response-SLA enforcement (7-day auto-delist)
v1.0 — Open, vendor-neutral schema extension for AI-readable job postings
FAQ
Where does the job data come from?
Directly from ~120 employers' own public ATS APIs (Greenhouse, Lever, Ashby, 北森 Beisen) — the same
endpoints that power their careers pages. No scraping, no third-party job boards. source is
always ats_public_api, and verified_at records the last time we confirmed each posting live.
Why should I trust ghost_score?
It's a pure, open, unpurchasable function — min(1, 0.15·relist_count + staleness) aged off the
real ATS posting date, not our crawl date. The formula lives in pipeline/ghost_score.py,
is unit-tested, and takes no money as input (red line #2). Long-open, repeatedly-relisted
postings score higher (worse); you can always re-rank client-side.
Does my résumé actually go through the server — really?
No. There is no résumé anywhere in the protocol. authorize_application has no résumé/file
parameter (it structurally cannot accept one), matching runs on your machine, and the only thing
that ever transits the server is a short anonymous fingerprint like #a3f9. This is enforced by
tests/test_privacy.py, and the published snapshot carries zero user data (tests/test_snapshot.py).
Does it support China (中国区)?
Yes, since v0.2: employers on 北森 Beisen (<tenant>.zhiye.com) are indexed — currently
11 robotics / embodied-AI companies (宇树 Unitree, 优必选 UBTECH, 星海图 Galaxea, 越疆 Dobot,
梅卡曼德 Mech-Mind, 普渡 Pudu, 海柔创新, 新松 SIASUN …). Pay published as 月薪 keeps its real
period (salary_period), so a salary floor no longer silently drops Chinese roles.
飞书招聘 (Feishu Hire) is not supported and won't be: it signs its job-list requests with a
ByteDance _signature and gates them behind a captcha SDK, so its listings are not publicly
readable. We don't break anti-bot measures. Moka is on the roadmap.
How do I get a company added?
Open a Company inclusion request issue (title it with the company + its ATS URL) — this is
the best way to contribute. If you code, add it to src/openhire/seed/candidates.py (company
slug + ATS vendor/tenant) and open a PR; the seeder validates tenants against the live API.
License
MIT © OpenHire Protocol · PRs welcome.
Built by a non-coder PM-ing Claude Code — full acceptance reports in reports/.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
Alicense-qualityAmaintenanceMCP server for job search and application tracking, enabling AI agents to search jobs, get details, manage applications, and find contacts across 128K+ jobs and 1,900+ companies.Last updated6431MIT- Alicense-qualityBmaintenanceAn MCP server that enables AI-assisted job search workflows including job discovery, application tracking, resume evaluation, and cover letter generation, with support for multiple job sources and scheduled scraping.Last updated581AGPL 3.0
- Alicense-qualityBmaintenanceA custom MCP server that exposes a jobs database to any MCP-compatible LLM client, allowing users to ask in plain English to search, filter, and match job openings.Last updatedMIT
- Alicense-qualityCmaintenanceMCP server that scours job openings from public, ToS-clean sources (Greenhouse, Lever, Ashby, HN, RemoteOK, Adzuna, USAJobs) and provides tools for job search, company listings, and salary context.Last updatedMIT
Related MCP Connectors
MCP server for AI job search — find jobs, track applications, get alerts. Claude, ChatGPT, Cursor.
GetJobzi MCP server for job search, application tracking, and career forecasting.
Managed LinkedIn MCP server for AI agents: search, connect, message and enrich on accounts you own.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/gzchenhao/openhire'
If you have feedback or need assistance with the MCP directory API, please join our Discord server