Agent Security Scanner MCP
Security scanner MCP server for AI coding agents. Prompt injection firewall, package hallucination detection (4.3M+ packages), 1000+ vulnerability rules with AST & taint analysis, auto-fix.
Is Agent Security Scanner MCP safe? Promising trust profile, but some evidence still deserves review.
Compare Agent Security Scanner MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Agent Security Scanner MCP scores 59.8/100 (Grade C), ranked #682 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.2/10; 71% of recent commits are signed; no published advisory affects its latest release (agent-security-scanner-mcp); last pushed 2026-10-14. Every point is earned from checkable signals — never paid placement. How scoring works →
How Agent Security Scanner MCP could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 74.5 B · #152 of 781
- Raise the OSSF Scorecard from 5.2 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +7.9 → 67.7 B · #251 of 781
- Sign every commit71% signed today +1.4 → 61.2 C · #352 of 781
Chain of custody
Scanners check what the code says. This traces who ships Agent Security Scanner MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/sinewaveai/agent-security-scanner-mcp, MIT, last pushed 2026-10-14. 71% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 5.2/10 (scanned Oct 7, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies1
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 0CI-Tests 9CII-Best-Practices 0Code-Review 0Contributors 6Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies 1SAST 8Security-Policy 10Signed-Releases -1Token-Permissions 0Vulnerabilities 0 -
Published packages Linked, not attested
- npm agent-security-scanner-mcp Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: agent-security-scanner-mcp 4.5.10. No published advisory affects it (OSV, checked 2026-10-16).
Changes to this chain
- 2026-08-27 OSSF Scorecard: 5.2/10
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Agent Security Scanner MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Agent Security Scanner MCP compares in MCP Servers
- #368 Replicant MCP 59.9 +0.1
- #369 Happy Platform MCP 59.8 ±0
- #370 Agent Security Scanner MCP 59.8 this agent
- #371 MCP Me 59.8 ±0
- #372 Home Assistant MCP 59.7 −0.1
Bars show each HVTrust score; the tick marks Agent Security Scanner MCP’s 59.8.
Where the 59.8 comes from
HVTrust dimensions vs the MCP Servers average
59.8 / 100 · 100.0% confidenceAgent Security Scanner MCP MCP Servers average (781 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
42.5 / 100Common questions about Agent Security Scanner MCP
Does Agent Security Scanner MCP publish package provenance?
Does Agent Security Scanner MCP have an OpenSSF Scorecard?
Is Agent Security Scanner MCP actively maintained?
What license does Agent Security Scanner MCP use?
Are Agent Security Scanner MCP's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Agent Security Scanner MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Agent Security Scanner MCP?
For maintainers
HVTrust scores Agent Security Scanner MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/agent-security-scanner-mcp)
<a href="https://hvtracker.net/agents/agent-security-scanner-mcp"><img src="https://hvtracker.net/badge/agent-security-scanner-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON