io.github.prPMDev/jd-intel-mcp
NPM · JD-INTEL-MCP · SCANNED SEP 20
Your AI fetches and reads full job descriptions across seven ATS platforms, no copy-paste.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 84 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1330 tokens (~332/item across 4 items; 3 tools + 1 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 Management93
- Stability observed for 28 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.prPMDev/jd-intel-mcp server?
io.github.prPMDev/jd-intel-mcp runs locally as an npm package, launched with npx -y jd-intel-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · jd-intel-mcp
claude mcp add prpmdev-jd-intel-mcp -- npx -y jd-intel-mcp
{
"mcpServers": {
"prpmdev-jd-intel-mcp": {
"command": "npx",
"args": [
"-y",
"jd-intel-mcp"
]
}
}
} {
"servers": {
"prpmdev-jd-intel-mcp": {
"command": "npx",
"args": [
"-y",
"jd-intel-mcp"
]
}
}
} codex mcp add prpmdev-jd-intel-mcp -- npx -y jd-intel-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"prpmdev-jd-intel-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"jd-intel-mcp"
],
"enabled": true
}
}
} openclaw mcp add prpmdev-jd-intel-mcp --command npx --arg -y --arg jd-intel-mcp
mcp_servers:
prpmdev-jd-intel-mcp:
command: "npx"
args: ["-y", "jd-intel-mcp"] {
"McpServers": {
"prpmdev-jd-intel-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"jd-intel-mcp"
]
}
}
} assistant mcp add prpmdev-jd-intel-mcp -t stdio -c npx -a -y jd-intel-mcp
{
"mcpServers": {
"prpmdev-jd-intel-mcp": {
"command": "npx",
"args": [
"-y",
"jd-intel-mcp"
]
}
}
} 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
- Security disclosure: unverified → fail ▼ functional
- 18 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
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 npm/jd-intel-mcp@0.8.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
detect_ats Detect which ATS a company uses ~262
Detect which ATS platform (Greenhouse, Lever, Ashby, SmartRecruiters, Teamtailor, Recruitee) a company uses by probing. Workday is registry-only and never returned here; find Workday-hosted companies via search_registry or fetch_jobs (which auto-detects 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"). RESPONSE: { status, data: "greenhouse" | "lever" | "ashby" | "smartrecruiters" | "teamtailor" | "recruitee" | null, metadata }. data === null means none of the probeable ATS host this company (Workday is registry-only and never detected here). "partial" status means some probes failed. Result may be incomplete. ERROR CODES: - invalid_args: company arg missing - partial_failure: some probes failed
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company name or slug |
No output schema declared.
No examples provided.
fetch_jobs Fetch jobs from a company ATS ~749
Fetch open job postings from a specific company's ATS (Greenhouse, Lever, Ashby, SmartRecruiters, Teamtailor, Recruitee, 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. 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. For US queries prefer ["United States", "US", "Remote - US"]. Avoid bare "Remote". It matches Remote-EMEA, Remote-LatAm. location_excludes: array. Drop jobs whose location contains any keyword. Use as refinement on top of includes. limit: default 100. Reduce for high-volume companies. workday: optional { tenant, env, site }. Use ONLY for a Workday company not in the registry when the user gives a careers URL. Derive from https://{tenant}.{env}.myworkdayjobs.com/{site}: tenant is the first label, env is the part like wd108, site is the path segment. Overrides the registry for that fetch. Never guess or fabricate these values; use only what the user supplied or what is literally in the careers URL. Omit this argument entirely if you do not h…
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company slug or name (e.g. "stripe") |
| filter | string | – | Regex matched across title, department, description — topic/scope |
| limit | integer | – | Cap results (default 100) |
| location_excludes | array | – | Drop jobs whose location contains any keyword |
| location_includes | array | – | Keep jobs whose location contains any keyword |
| posted_within_days | integer | – | Only jobs posted within N days |
| title_filter | string | – | Regex matched against title only — role identity |
| workday | object | – | Override the registry for a Workday board not indexed. Derive all three from the careers URL https://{tenant}.{env}.myworkdayjobs.com/{site}. Never guess these. |
No output schema declared.
No examples provided.
search_registry Search the company registry ~217
Find companies in the indexed registry by name or sector. USE WHEN: targeted lookups ("Is Stripe in your index?", "Show me fintech companies"). DON'T USE WHEN: - User wants a broad survey of the catalog → read the registry://jd-intel/all Resource instead (one fetch vs repeated tool calls) - User asks about a specific company's jobs → call fetch_jobs directly ARGUMENT GUIDE: query: optional. Substring match (case-insensitive) against company name. sector: optional. Match against sector field. Examples: "fintech", "developer tools", "marketing tech". At least one argument required. Returns companies matching either. RESPONSE: { status, data: [{ slug, name, sector, ats }], metadata }. Each result includes the ATS platform for that company. ERROR CODES: - invalid_args: both query and sector missing
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Substring match against company name |
| sector | string | – | Match against sector (e.g. "fintech", "developer tools") |
No output schema declared.
No examples provided.
What is the io.github.prPMDev/jd-intel-mcp server?
io.github.prPMDev/jd-intel-mcp is listed in the public MCP registry as io.github.prPMDev/jd-intel-mcp. Your AI fetches and reads full job descriptions across seven ATS platforms, no copy-paste. This page covers its npm package (jd-intel-mcp).
Is the io.github.prPMDev/jd-intel-mcp server safe to use?
io.github.prPMDev/jd-intel-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.prPMDev/jd-intel-mcp server expose?
io.github.prPMDev/jd-intel-mcp exposes 3 tools: fetch_jobs, search_registry, detect_ats. Their descriptions and schemas cost roughly 1,228 tokens of context every time the server is loaded.
Is the io.github.prPMDev/jd-intel-mcp server still maintained?
io.github.prPMDev/jd-intel-mcp 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 io.github.prPMDev/jd-intel-mcp server under?
io.github.prPMDev/jd-intel-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.