agent-security-scanner-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 4 of 4 tools tried
Contacts while installing and starting: api.proof-layer.com
What it contacted
api.proof-layer.com
Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.
Starting it
npx -y -p agent-security-scanner-mcp@4.5.10 agent-security-scanner-mcp
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
4 tools that take no input and look read-only were called once with nothing. 4 returned a result.
list_security_rules | Returned a result under 0.1 s · 13,478 characters |
list_package_stats | Returned a result under 0.1 s · 1,270 characters |
clawproof_health | Returned a result under 0.1 s · 1,464 characters |
get_compliance_controls | Returned a result under 0.1 s · 9,256 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
scan_security file_path, output_format, verbosity, engine, project_context, include_context, enable_semantic
Scan a file for security vulnerabilities. Use verbosity='minimal' for counts only (~50 tokens), 'compact' (default) for actionable info (~200 tokens), 'full' for complete metadata.
fix_security file_path, verbosity
Scan a file and return fixes. Use verbosity='minimal' for summary only, 'compact' (default) for fix list, 'full' for complete fixed file content.
record_security_outcome accepted_count, dismissed_count, fixed_count
Record aggregate remediation outcomes after reviewing scanner findings. Sends counts only; never sends code, findings, paths, or rule IDs.
list_security_rules
List all available security fix templates and their descriptions
check_package package_name, ecosystem
Check if a package name is legitimate or potentially hallucinated (AI-invented)
18 more tools
scan_packages file_path, ecosystem, verbosity
Scan code for package imports and check for hallucinated (AI-invented) packages. Use verbosity='minimal' for counts, 'compact' (default) for flagged packages, 'full' for all details.
list_package_stats
List statistics about loaded package lists for hallucination detection
scan_agent_prompt prompt_text, context, verbosity
Scan a prompt for malicious intent. Returns BLOCK/WARN/LOG/ALLOW. Use verbosity='minimal' for action only, 'compact' (default) for findings, 'full' for audit details.
scan_git_diff base_ref, target_ref, verbosity
Scan git diff for new security vulnerabilities. Only reports issues on changed lines. Use for PR reviews.
scan_project directory_path, recursive, include_patterns, exclude_patterns, diff_only, cross_file, verbosity
Scan an entire directory for security vulnerabilities with .gitignore support and security grading. Use verbosity='minimal' for grade + counts, 'compact' (default) for top issues, 'full' for all details.
scan_agent_action action_type, action_value, verbosity
Pre-execution security check for agent actions (bash, file_write, file_read, http_request, file_delete, cron, process_spawn, git, docker). Returns ALLOW/WARN/BLOCK.
scan_mcp_server server_path, verbosity, manifest, update_baseline
Scan an MCP server's source code for security vulnerabilities: overly broad permissions, missing input validation, data exfiltration, insecure patterns. Returns grade (A-F) and recommendations.
scan_skill skill_path, verbosity, baseline
Deep security scan of an OpenClaw skill. Multi-layer analysis: prompt injection detection, code analysis (AST+taint), ClawHavoc malware signatures, package supply chain verification, rug pull detection. Returns security grade A-F with detailed findings.
scanner_health
Check plugin health: engine status, daemon status, package data availability
clawproof_health
Alias for scanner_health (deprecated, use scanner_health instead)
score_aivss findings, source_tool, overrides, verbosity
Score findings using OWASP AIVSS v2. Accepts any scanner output or raw findings JSON. Returns per-finding AIVSS scores (0-10) and aggregate posture. Use verbosity='minimal' for posture only, 'compact' (default) for scores, 'full' for all metrics.
get_compliance_controls framework, domain, control_ids, owasp_filter, verbosity
Look up compliance controls with evaluation criteria. Supports multiple frameworks: aiuc-1 (default), soc2-technical, gdpr-technical. Filter by domain, control IDs, or OWASP LLM tags.
evaluate_compliance directory_path, frameworks, sbom_path, baseline_path, save_evidence, verbosity
Evaluate a project against compliance frameworks (SOC2-technical, GDPR-technical, AIUC-1). Collects evidence from code scans, SBOM, vulnerability checks, and hallucination detection, then evaluates controls. Optionally saves timestamped evidence bundle.
sbom_generate directory_path, include_dev, output_path, verbosity
Generate a CycloneDX v1.5 SBOM for a project. Discovers all dependencies (direct + transitive) from lock files and manifests across Node.js, Python, Go, Rust, Ruby, Java. Use verbosity='minimal' for counts, 'compact' (default) for component list, 'full' for complete CycloneDX JSON.
sbom_scan_vulnerabilities directory_path, sbom_path, severity_threshold, verbosity
Cross-reference SBOM components against OSV.dev vulnerability database. Returns CVE IDs, CVSS scores, severity, and fix recommendations. Accepts directory_path (generates fresh) or sbom_path (loads saved artifact).
sbom_check_hallucinations directory_path, sbom_path, verbosity
Check all packages in an SBOM against official registries to detect hallucinated (AI-invented) package names. Supports npm, pypi, rubygems, dart, perl, raku, crates. Go/Java marked as unsupported.
sbom_diff directory_path, baseline_path, save_baseline, verbosity
Compare current project SBOM against a stored baseline. Reports added, removed, and version-changed packages. Use save_baseline=true to create initial baseline.
sbom_export_report directory_path, sbom_path, format, include_vulnerabilities, output_path, verbosity
Generate an HTML or JSON audit report from SBOM data, optionally enriched with vulnerability scan results. Suitable for PCI-DSS and compliance audits.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Files it wrote
/tmp/ .prooflayer/ anonymous-install-id
Paths inside its sandbox, where its home folder is /tmp and its own folder cannot be written to.
Install facts
| License | MIT |
|---|---|
| Needs | node >=18.0.0 |
| Source | github.com/sinewaveai/agent-security-scanner-mcp |
| Install scripts | agent-security-scanner-mcp declare them. This runner does not run them. |
| Tarball | sha512-GiSEMBdcz5r0fQt6R5S7HCmhkBhrWjk9koCeeZ0QpSPzZpTzGt4fbkaBB3v5Y42WcIUb6W4YYYwtoQrnG0+lVg== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/agent-security-scanner-mcp)
New version out? Ask for a fresh report.