agent-security-scanner-mcp
agent-security-scanner-mcp is an MCP server published by sinewaveai, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does agent-security-scanner-mcp support the current MCP specification (2026-07-28)?
Not yet confirmed. agent-security-scanner-mcp is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is agent-security-scanner-mcp a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for agent-security-scanner-mcp (as of 2026-08-20).
How do I connect to agent-security-scanner-mcp?
agent-security-scanner-mcp is available via the package npm:agent-security-scanner-mcp, the official MCP Registry under io.github.sinewaveai/agent-security-scanner-mcp, the source repository at https://github.com/sinewaveai/agent-security-scanner-mcp. Authentication: unknown. Transports: stdio.
Does agent-security-scanner-mcp support MCP revision 2025-11-25?
Yes. agent-security-scanner-mcp supports MCP revision 2025-11-25 (checked 2026-08-20).
Does agent-security-scanner-mcp support MCP revision 2026-07-28?
No. agent-security-scanner-mcp was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were agent-security-scanner-mcp's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Security layer for AI agents: blocks prompt injection, detects fake packages, scans vulnerabilities.
Which MCP spec revisions does agent-security-scanner-mcp support?
agent-security-scanner-mcp has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is agent-security-scanner-mcp?
Ranked #225 in The MCP 500 with Adoption Index 50.34 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 508 | API · |
| GitHub stars | 122 | API · |
| GitHub forks | 11 | API · |
| Last push | 2026-09-10T21:03:34Z | API · |
| Repository archived | no | API · |
Repository and package signals for agent-security-scanner-mcp
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 14
- Primary language
- JavaScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- Present
Declared topics: agent-security, ai-agent-security, ai-security, claude-code, codex, cursor, hallucination-detection, llm-security, mcp, mcp-security, mcp-server, openclaw, owasp, package-hallucination, prompt-injection, sast, security, supply-chain-security, vulnerability-scanner, windsurf — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
4.5.9- Last published
- First published
- Releases
- 81
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 5
- Unpacked size
- 18.7 MB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.sinewaveai/agent-security-scanner-mcp at version 2.0.1 - lists package npm:agent-security-scanner-mcp and repository https://github.com/sinewaveai/agent-security-scanner-mcp - accessed
- npm registry metadata for agent-security-scanner-mcp at published version 4.5.9, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed