io.github.prPMDev/jd-intel-mcp

List the ATS platforms a company answers on: registry rows first (all nine platforms, Workday included, no request made), then a live probe of every probeable ATS (Greenhouse, Lever, Ashby, SmartRecruiters, Teamtailor, Recruitee, Personio, Workable) the registry did not list. Workday cannot be probed, so a Workday board appears only from the registry. USE WHEN: user asks about the ATS platform explicitly ("What ATS does Stripe use?") or for debugging. DON'T USE WHEN: you want to fetch jobs. Call fetch_jobs directly (it auto-detects internally). ARGUMENT GUIDE: company: company name or slug. Hyphens and spaces stripped automatically ("Cockroach Labs" → "cockroachlabs"). A missing or non-string company or an unknown key fails the input schema and returns isError with plain text naming the field and no envelope; fix that argument and call again. RESPONSE: { status, data: "greenhouse" | "lever" | "ashby" | "smartrecruiters" | "teamtailor" | "recruitee" | "personio" | "workable" | "workday" | null, metadata: { attempted, succeeded, boards, failed, notes } }. boards: every board known for this slug, [{ ats, slug, source }], in platform order. source "registry": a registry row, not probed. source "probe": the ATS answered to this slug live; the registry does not vouch that it is the company asked about. A listed board exists and may hold zero postings. data: the ats of the first board, null when boards is empty. succeeded: the ats of each board. attempted: the ATS probed live (every probeable ATS the registry did not list). failed: probes that could not be checked, [{ ats, slug, code, message }]; a failed probe is neither a match nor a miss. notes: present only when boards spans several platforms, stating that data is the first in platform order, not a ranking, and that every board is in metadata.boards. STATUSES: - success: every probe completed (failed is empty). data null with boards empty means no registry row and no probeable ATS answered. - partial: at least…

Fetch open job postings from one company's ATS board (Greenhouse, Lever, Ashby, SmartRecruiters, Teamtailor, Recruitee, Personio, Workable, Workday). USE WHEN: the user asks about roles at a known company ("Is Stripe hiring?", "What's open at Figma?"). DON'T USE WHEN: - User doesn't know the company → read the registry Resource or call search_registry - User only asks which ATS a company uses → call detect_ats ARGUMENT GUIDE: company: lowercase slug, no spaces (e.g. "stripe", "cockroachlabs"). Hyphens and spaces auto-stripped. A registry slug costs one board fetch; any other slug is probed on every probeable ATS. title_filter: JavaScript-compatible regex matched against TITLE ONLY. Case-insensitive by default. Do NOT use inline flags like (?i) (not supported by V8). Use for role identity ("product manager", "staff engineer"). Does NOT match description text. That's the distinction from filter. filter: JavaScript-compatible regex matched across title + department + description. Case-insensitive by default. Do NOT use inline flags like (?i). Use for topic/scope ("integrations", "growth"). AND'd with title_filter. posted_within_days: number. "recent" or "new" → 30. "this week" → 7. "today" → 1. location_includes: array of keywords. Case-insensitive substring match; short codes (US, UK) use word-boundary matching automatically. Checked against every entry of a job's locations array: a job open in Berlin and New York matches ["New York"]. For US queries prefer ["United States", "US", "Remote - US"]. Avoid bare "Remote". It matches Remote-EMEA, Remote-LatAm. location_excludes: array. Drops a job only when every one of its locations matches a keyword: the Berlin and New York job survives ["US"] because it is still open in Berlin, and drops under ["Germany", "US"]. Use as refinement on top of includes. limit: max jobs per page, default 100. max_tokens usually stops output first, so on a large board a default call returns a few complete postings. total_matched and…

Find companies in the indexed registry by name or sector. USE WHEN: a company name or a sector word is in hand ("Is Stripe in your index?", "Show me fintech companies"). DON'T USE WHEN: - User wants the whole catalog, across every sector → read the registry://jd-intel/all Resource instead (one large read) - User asks about a specific company's jobs → call fetch_jobs directly ARGUMENT GUIDE: query: optional. Case-insensitive substring match against company name or sector. sector: optional. Case-insensitive substring match against sector only ("fintech", "developer tools"). limit: optional. Max rows returned, default 50, max 200. At least one is required. Passing both narrows: a row must match query (on name or sector) and sector (AND). An argument that fails the input schema (wrong type, unknown key) returns isError with plain text naming the field and no envelope; fix that argument and call again. RESPONSE: { status, data: [{ slug, name, sector, ats }] | null, metadata: { count, total, truncated, query, sector, version, registry_source } }. Each row is one board; ats is the platform it is on. Rows are ranked: an exact name or slug, then names starting with the query, then names containing it, then sector-only matches. count is rows in data. total is every row that matched. truncated: null, or { reason: "limit", not_returned } when more matched than limit; narrow the term or combine query with sector before raising limit. query and sector echo the arguments, null when not passed. registry_source is "network", "disk-fallback" (the bundled copy) or "mixed". STATUSES: - success: the registry was searched. data may be []. - error: data is null and error.code says why. ERROR CODES: - invalid_args: both query and sector missing. - internal_error: an exception inside the server, not an argument problem.