openhire 0.1.1

OpenHire v0.1 「哨兵」— an MCP job protocol server. Résumés never leave your device.

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 remote AI / Infra roles — sourced directly from ~100 company career sites and their public ATS APIs (Greenhouse / Lever / Ashby). 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 v0.1 「哨兵 / 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 serve

For Claude Desktop, add to claude_desktop_config.json:

{
  "mcpServers": {
    "openhire": {
      "command": "ohp",
      "args": ["serve"]
    }
  }
}

On Windows the config file lives at %APPDATA%\Claude\claude_desktop_config.json (for the Microsoft Store build it is under …\Packages\<Claude package>\LocalCache\Roaming\Claude\). Fully quit and reopen Claude Desktop after editing.

---

What it does

Tool	What it gives you
search_jobs	Hard-filter the live index; every result carries verified_at, datePosted, days_open, ghost_score, remote_scope, eligible_regions, apply_channel. Filter by required_skills (AND), role_family, remote_scope, min_salary + currency.
watch_intent	Register a standing intent once — new matching jobs are waiting next time you check, even after you close the terminal. Accepts required_skills / role_family so sales / solutions roles stay out.
check_watches	Pull the matches that are new since your last check (client-pull; stdio has no push).
authorize_application	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é.
get_company_info	Aggregate, anonymous trust signals for one employer (ghost_score_avg, active_jobs, index_built_at). Never any candidate data.

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 site
• source — 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

1. Your résumé stays on your machine — it never transits the server, and we never store it.
2. Ranking is not for sale — it is only f(match_quality, freshness), a locked pure function.
3. 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 green

Set 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_score public beta
• v0.3 — Employer claim + verified badges · response-SLA enforcement (7-day auto-delist)
• v1.0 — Open, vendor-neutral schema extension for AI-readable job postings

License

MIT © OpenHire Protocol · PRs welcome.