Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.XJTLUmedia/ai-hr-management-toolkit

NPM · MCP-AI-HR-MANAGEMENT-TOOLKIT · SCANNED AUG 3

AI HR toolkit: 24 MCP tools for resume parsing, skill extraction & ATS management.

+8 this week 32 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security75
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects next 16.2.2, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (250 of 356), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · mcp-ai-hr-management-toolkit

# add to Claude Code
claude mcp add xjtlumedia-ai-hr-management-toolkit -- npx -y mcp-ai-hr-management-toolkit
# add to Codex CLI
codex mcp add xjtlumedia-ai-hr-management-toolkit -- npx -y mcp-ai-hr-management-toolkit
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xjtlumedia-ai-hr-management-toolkit": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-ai-hr-management-toolkit"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add xjtlumedia-ai-hr-management-toolkit --command npx --arg -y --arg mcp-ai-hr-management-toolkit
# ~/.hermes/config.yaml
mcp_servers:
  xjtlumedia-ai-hr-management-toolkit:
    command: "npx"
    args: ["-y", "mcp-ai-hr-management-toolkit"]
// mcp.json
{
  "mcpServers": {
    "xjtlumedia-ai-hr-management-toolkit": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-ai-hr-management-toolkit"
      ]
    }
  }
}
Changelog

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.

  • 3 Aug 26 +1
    • CVE-2026-45109 affects this package: high security
    • GHSA-f88m-g3jw-g9cj affects this package: high security
    • CVE-2026-12151 affects this package: high security
    • CVE-2026-64648 affects this package: high security
    • CVE-2026-64645 affects this package: high security
    • CVE-2026-64641 affects this package: high security
    • CVE-2026-64643 affects this package: high security
    • CVE-2026-44574 affects this package: high security
    • CVE-2026-44580 affects this package: high security
    • CVE-2026-64649 affects this package: high security
    • CVE-2026-44581 affects this package: high security
    • CVE-2026-44572 affects this package: high security
    • GHSA-q4gf-8mx6-v5v3 affects this package: high security
    • CVE-2026-44579 affects this package: high security
    • GHSA-p6gq-j5cr-w38f affects this package: high security
    • CVE-2026-41305 affects this package: high security
    • GHSA-8h8q-6873-q5fj affects this package: high security
    • CVE-2026-22036 affects this package: high security
    • CVE-2026-1527 affects this package: high security
    • CVE-2026-1525 affects this package: high security
    • CVE-2026-44576 affects this package: high security
    • CVE-2026-64642 affects this package: high security
    • CVE-2026-44582 affects this package: high security
    • GHSA-r28c-9q8g-f849 affects this package: high security
    • CVE-2026-64644 affects this package: high security
    • CVE-2026-64646 affects this package: high security
    • CVE-2026-41907 affects this package: high security
    • CVE-2026-44573 affects this package: high security
    • CVE-2026-1526 affects this package: high security
    • CVE-2026-44575 affects this package: high security
    • CVE-2026-11525 affects this package: high security
    • CVE-2026-64647 affects this package: high security
    • CVE-2026-45623 affects this package: high security
    • CVE-2026-9679 affects this package: high security
    • CVE-2026-2229 affects this package: high security
    • CVE-2026-44577 affects this package: high security
    • CVE-2026-44578 affects this package: high security
    • CVE-2026-6733 affects this package: high security
  • 2 Aug 26 +26
    • GHSA-f88m-g3jw-g9cj affects this package: high security
    • CVE-2026-45109 affects this package: high security
    • CVE-2026-44580 affects this package: high security
    • CVE-2026-64649 affects this package: high security
    • CVE-2026-44581 affects this package: high security
    • CVE-2026-44572 affects this package: high security
    • GHSA-q4gf-8mx6-v5v3 affects this package: high security
    • CVE-2026-44579 affects this package: high security
    • GHSA-p6gq-j5cr-w38f affects this package: high security
    • CVE-2026-41305 affects this package: high security
    • GHSA-8h8q-6873-q5fj affects this package: high security
    • CVE-2026-22036 affects this package: high security
    • CVE-2026-1527 affects this package: high security
    • CVE-2026-1525 affects this package: high security
    • CVE-2026-44576 affects this package: high security
    • CVE-2026-64642 affects this package: high security
    • CVE-2026-44582 affects this package: high security
    • GHSA-r28c-9q8g-f849 affects this package: high security
    • CVE-2026-64644 affects this package: high security
    • CVE-2026-64646 affects this package: high security
    • CVE-2026-41907 affects this package: high security
    • CVE-2026-44573 affects this package: high security
    • CVE-2026-1526 affects this package: high security
    • CVE-2026-44575 affects this package: high security
    • CVE-2026-11525 affects this package: high security
    • CVE-2026-64647 affects this package: high security
    • CVE-2026-45623 affects this package: high security
    • CVE-2026-9679 affects this package: high security
    • CVE-2026-2229 affects this package: high security
    • CVE-2026-44577 affects this package: high security
    • CVE-2026-44578 affects this package: high security
    • CVE-2026-6733 affects this package: high security
    • CVE-2026-44574 affects this package: high security
    • CVE-2026-64643 affects this package: high security
    • CVE-2026-64641 affects this package: high security
    • CVE-2026-64645 affects this package: high security
    • CVE-2026-64648 affects this package: high security
    • CVE-2026-12151 affects this package: high security
    • Provenance: unverified → fail security
    • Known CVEs: unverified → fail security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare. security
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Licence: MIT functional
  • 1 Aug 26 −1
    • Dependency health: partial → unverified functional
  • 31 Jul 26 −18
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 0
    • Security disclosure: unverified → fail functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
  • 27 Jul 26 24

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Vulnerabilities 38 findings
ID CVE Severity Vector Fix available
GHSA-267c-6grr-h53f CVE-2026-44575 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-26hh-7cqf-hhc6 CVE-2026-45109 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-36qx-fr4f-26g5 CVE-2026-44573 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-3g8h-86w9-wvmq CVE-2026-44572 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-4633-3j49-mh5q CVE-2026-64647 medium yes
GHSA-492v-c6pp-mqqv CVE-2026-44574 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-4c39-4ccg-62r3 CVE-2026-64646 medium yes
GHSA-68g3-v927-f742 CVE-2026-64648 medium yes
GHSA-6gpp-xcg3-4w24 CVE-2026-64642 high yes
GHSA-89xv-2m56-2m9x CVE-2026-64649 high yes
GHSA-8h8q-6873-q5fj high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-955p-x3mx-jcvp CVE-2026-64643 medium yes
GHSA-c4j6-fc7j-m34r CVE-2026-44578 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N yes
GHSA-ffhc-5mcf-pf4q CVE-2026-44581 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N yes
GHSA-gx5p-jg67-6x7h CVE-2026-44580 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes
GHSA-h64f-5h5j-jqjh CVE-2026-44577 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-m99w-x7hq-7vfj CVE-2026-64641 high yes
GHSA-mg66-mrh9-m8jx CVE-2026-44579 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-p9j2-gv94-2wf4 CVE-2026-64645 high yes
GHSA-q4gf-8mx6-v5v3 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-q8wf-6r8g-63ch CVE-2026-64644 medium yes
GHSA-vfv6-92ff-j949 CVE-2026-44582 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-wfc6-r584-vfw7 CVE-2026-44576 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:L yes
GHSA-p6gq-j5cr-w38f high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-6g55-p6wh-862q CVE-2026-45623 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-qx2v-qp2m-jg93 CVE-2026-41305 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes
GHSA-r28c-9q8g-f849 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-f88m-g3jw-g9cj high yes
GHSA-2mjp-6q6p-2qxm CVE-2026-1525 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-35p6-xmwp-9g52 CVE-2026-6733 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-4992-7rv2-5pvq CVE-2026-1527 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N yes
GHSA-g8m3-5g58-fq7m CVE-2026-11525 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-g9mf-h72j-4rw9 CVE-2026-22036 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-p88m-4jfj-68fv CVE-2026-9679 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-v9p9-hfj2-hcw8 CVE-2026-2229 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vrm6-8vpv-qv8q CVE-2026-1526 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vxpw-j846-p89q CVE-2026-12151 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
Dependencies 250 packages

250 packages in the resolved dependency tree · 155 deprecated · 64 stale · 2 without a linked repository.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools

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.

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.