@autostackup/hr

MCPcommunity

v0.1.2UnknownMITUpdated 4mo agonpm GitHub

The only HR MCP you'll ever need. Professionally built candidate screening with structured competency scoring, 30/60/90-day onboarding plans, offer letter generation, interview kits, and performance reviews — frameworks used by top People teams, all insid

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

72Downloads/wk

4mo agoLast update

Package

AuthorUnknown

LicenseMIT

Version0.1.2

Sourcenpm+mcp-registry

npm@autostackup/hr

GitHubAutostackup/autostackup

SBOMCycloneDX 1.6 ↓

Trust Status

B

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface5 tools · 1 privileged

Security scan✓ Cleanv0.1.2 · 1mo agoHow well does this scan work?

EvalsNone

IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

5 tools · 1 privileged

Statically extracted from the published packagev0.1.2 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

screen_candidateScore a candidate against a job's required skills, experience, and must-haves. Returns a tier (A/B/C/D), skill gap analysis, salary fit, and exact recommended next step. Built on structured competency scoring used by top People teams.

Score a candidate against a job's required skills, experience, and must-haves. Returns a tier (A/B/C/D), skill gap analysis, salary fit, and exact recommended next step. Built on structured competency scoring used by top People teams.

No input schema was published for this tool.

draft_offer_letterGenerate a professional, ready-to-send offer letter with compensation summary, equity and bonus clauses, expiry date, negotiation notes, and a follow-up call script. Supports formal, warm, and startup tones.

Generate a professional, ready-to-send offer letter with compensation summary, equity and bonus clauses, expiry date, negotiation notes, and a follow-up call script. Supports formal, warm, and startup tones.

No input schema was published for this tool.

create_onboarding_planBuild a complete 30/60/90-day onboarding plan for a new hire. Includes Day 1 checklist, weekly themes, milestone goals, manager action list, red flag warnings, and a success definition. Adapts for IC, manager, and executive roles.

Build a complete 30/60/90-day onboarding plan for a new hire. Includes Day 1 checklist, weekly themes, milestone goals, manager action list, red flag warnings, and a success definition. Adapts for IC, manager, and executive roles.

No input schema was published for this tool.

build_interview_kitGenerate a complete interview kit for any role — structured questions by competency, STAR follow-up probes, 'what good looks like' benchmarks, red flags, a scorecard template, legal reminders, and a debrief guide. Covers screening, technical, behavioural, case, panel, and final interviews.

Generate a complete interview kit for any role — structured questions by competency, STAR follow-up probes, 'what good looks like' benchmarks, red flags, a scorecard template, legal reminders, and a debrief guide. Covers screening, technical, behavioural, case, panel, and final interviews.

No input schema was published for this tool.

write_performance_reviewprivilegedWrite a structured performance review with achievements narrative, development sections, next-period goals, compensation recommendation, and a manager meeting guide. Adapts to exceeds/meets/partially meets/does not meet ratings and supports coaching, direct, and formal tones.

Write a structured performance review with achievements narrative, development sections, next-period goals, compensation recommendation, and a manager meeting guide. Adapts to exceeds/meets/partially meets/does not meet ratings and supports coaching, direct, and formal tones.

No input schema was published for this tool.

5 of 5 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

The only HR MCP you'll ever need. Professionally built candidate screening with structured competency scoring, 30/60/90-day onboarding plans, offer letter generation, interview kits, and performance reviews — frameworks used by top People teams, all insid

Keywords

mcpautostackuphrrecruitingonboardinghiringpeople-ops

Alternatives

Comparing tool surfaces…

Tools exposed

5 tools · 1 privileged · observed 2026-08-30 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-30 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod3.25.76
@autostackup/core0.1.12 dependencies
- @modelcontextprotocol/sdk1.30.017 dependencies
  - ajv8.20.04 dependencies
    fast-deep-equal3.1.3
    fast-uri3.1.6
    json-schema-traverse1.0.0
    require-from-string2.0.2
  - zod4.5.4
  - cors2.8.6+2 not drawn
  - hono4.13.5
  - jose6.2.10
  - express5.2.1+27 not drawn1 dependency
    content-type1.0.5
  - raw-body3.0.2+4 not drawn
  - ajv-formats3.0.11 dependency
    ajv8.20.0shown above
  - cross-spawn7.0.6+3 not drawn
  - eventsource3.0.71 dependency
    eventsource-parser3.1.1
  - content-type1.0.5shown above
  - pkce-challenge5.0.1
  - @hono/node-server2.1.1
  - json-schema-typed8.0.2
  - eventsource-parser3.1.1shown above
  - express-rate-limit8.7.0+2 not drawn
  - zod-to-json-schema3.25.2
- zod3.25.76shown above
@modelcontextprotocol/sdk1.30.0shown above

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

55 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 50
below the depth cap: 5

es-define-property ^1.0.1 — required by qs@6.16.0package cap reached
wrappy 1 — required by once@1.4.0package cap reached
http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached

+43 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.