@sicks3c/hackerone-mcp-server
BMCP server package hackerone-mcp-server
Install
agr install @sicks3c/hackerone-mcp-server --target claudeThis artifact does not publish files for Claude.
Document
{ "name": "hackerone-mcp-server", "version": "1.0.0", "description": "MCP server for accessing HackerOne reports in Claude Code", "type": "module", "main": "dist/index.js", "bin": { "hackerone-mcp-server": "dist/index.js" }, "scripts": { "build": "tsc", "start": "node dist/index.js", "dev": "tsx src/index.ts" }, "dependencies": { "@modelcontextprotocol/sdk": "^1.0.0", "node-fetch": "^3.3.2", "zod": "^3.22.0" }, "devDependencies": { "@types/node": "^20.0.0", "tsx": "^4.7.0", "typescript": "^5.3.0" } }
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- warnType matchbest-effort: server code not analyzed
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicenseno SPDX license detected
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-66877efa7af52026-08-03