io.github.sinewaveai/agent-security-scanner-mcp
NPM · AGENT-SECURITY-SCANNER-MCP · SCANNED AUG 3
Security layer for AI agents: blocks prompt injection, detects fake packages, scans vulnerabilities.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (104 of 108), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (104 of 108), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 355 tokens (~50/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · agent-security-scanner-mcp
claude mcp add sinewaveai-agent-security-scanner-mcp -- npx -y agent-security-scanner-mcp
codex mcp add sinewaveai-agent-security-scanner-mcp -- npx -y agent-security-scanner-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sinewaveai-agent-security-scanner-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"agent-security-scanner-mcp"
],
"enabled": true
}
}
} openclaw mcp add sinewaveai-agent-security-scanner-mcp --command npx --arg -y --arg agent-security-scanner-mcp
mcp_servers:
sinewaveai-agent-security-scanner-mcp:
command: "npx"
args: ["-y", "agent-security-scanner-mcp"] {
"mcpServers": {
"sinewaveai-agent-security-scanner-mcp": {
"command": "npx",
"args": [
"-y",
"agent-security-scanner-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +33
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.20 ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Licence: MIT functional
- 31 Jul 26 −26
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 29 Jul 26 +50
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Security disclosure: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- Licence: MIT functional
- 28 Jul 26 +3
- Security disclosure: fail → unverified ▼ functional
- 27 Jul 26 25
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 104 packages
104 packages in the resolved dependency tree · 99 deprecated · 36 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
check_package ~90
Check if a package name is legitimate or potentially hallucinated (AI-invented)
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | The package ecosystem (dart=pub.dev, perl=CPAN, raku=raku.land, npm=npmjs, pypi=PyPI, rubygems=RubyGems, crates=crates.io) |
| package_name | string | yes | The package name to verify |
No output schema declared.
No examples provided.
fix_security ~36
Scan a file and return the fixed content with all security issues resolved
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the file to fix |
No output schema declared.
No examples provided.
list_package_stats ~20
List statistics about loaded package lists for hallucination detection
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_security_rules ~19
List all available security fix templates and their descriptions
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_agent_prompt ~63
Scan a prompt/instruction for potential malicious intent before execution. Returns risk assessment and recommended action (BLOCK/WARN/LOG/ALLOW).
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | — | Optional context for better analysis |
| prompt_text | string | yes | The prompt or instruction text to analyze |
No output schema declared.
No examples provided.
scan_packages ~92
Scan code for package imports and check for hallucinated (AI-invented) packages
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | The package ecosystem (dart=pub.dev, perl=CPAN, raku=raku.land, npm=npmjs, pypi=PyPI, rubygems=RubyGems, crates=crates.io) |
| file_path | string | yes | Path to the file to scan |
No output schema declared.
No examples provided.
scan_security ~35
Scan a file for security vulnerabilities and return issues with suggested fixes
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the file to scan |
No output schema declared.
No examples provided.