Deephr Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Deephr Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Read-only MCP server exposing deepHR's modules to MCP clients (Claude Desktop / Claude Code). It proxies read calls to the deepHR backend /api/* over HTTP, authenticating with a service account and refreshing the JWT on 401.
No clone needed — run it straight from GitHub with npx:
claude mcp add deephr -s user \
-e DEEPHR_API_URL=https://deephr.your-cloud-domain.com \
-e [email protected] \
-e DEEPHR_PASSWORD=... \
-- npx -y github:leevydanomalik/deephr-mcp(If/when published to npm, swap the last line for npx -y deephr-mcp.)
-s user makes it global (available in every project on that machine). Each user only changes DEEPHR_API_URL (the deployed backend) and their own login. Needs Node >= 18.
The config tracks the main branch, so a new release is just a new commit here. Two things to know when pulling an update:
npxcommand, but npx may relaunch a cached older build instead of re-fetching main. To guarantee you get the latest, clear the cache first, then reconnect:
rm -rf ~/.npm/_npx # drop npx's cached git installs(Alternatively pin a commit — npx -y github:leevydanomalik/deephr-mcp#<sha> — for a deterministic install, at the cost of editing config each release.)
call new /api/* endpoints. The backend at your DEEPHR_API_URL must be running a version that has them, or the new operations return 404. Updating the MCP client alone is not enough.
[email protected] DEEPHR_PASSWORD=... bun run src/server.tsThe backend must be running (default http://localhost:4445).
bun run build # bundles src/ -> dist/server.js (node ESM, shebang, npx-runnable)
npm publish # prepublishOnly runs the build automaticallydeephr-mcp is an unscoped public package — npm login once, then npm publish.
| Var | Default | Purpose |
|---|---|---|
DEEPHR_API_URL | http://localhost:4445 | Backend base URL |
DEEPHR_EMAIL | (required) | Service-identity login (use an admin/superadmin account) |
DEEPHR_PASSWORD | (required) | Service-identity password |
{
"mcpServers": {
"deephr": {
"command": "bun",
"args": ["run", "/ABSOLUTE/PATH/deepHR/mcp/src/server.ts"],
"env": {
"DEEPHR_API_URL": "http://localhost:4445",
"DEEPHR_EMAIL": "[email protected]",
"DEEPHR_PASSWORD": "..."
}
}
}
}~16 facade tools (deephr_payroll, deephr_employees, …). Each takes { operation, params }. See a tool's description for its operation catalog.
Routes are scanned from backend/src/app/api:
bun run scan # regenerates src/registry/<facade>.ts + index.tsHand-tune hot operations (better summaries, real query schemas) in src/registry/annotations.ts — that layer survives re-scans.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.