vulnerability-scanner
Triggers GuardBee scans, queries findings, AI-assisted remediation guidance
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: scan code for vulnerabilities.Similar tools
Listed for the same task: scan code for vulnerabilitiesReviews
No review yet. Used vulnerability-scanner? Be the first to help others choose.What it does
vulnerability-scanner is an MCP server, a connector that lets an AI assistant use it as a tool. It is installed locally as a package and runs on your machine.
From the publisher's description, Electra Index matched it to one capability: security scanning. That makes it a candidate for tasks such as scan code for vulnerabilities or review pull requests.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · not tested by Electra IndexInstall package
- NPM
@guardbee/mcp-vulnerability-scannerv0.4.1 · runs locally (stdio)
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"vulnerability-scanner": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-vulnerability-scanner"
]
}
}
}Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Install package | @guardbee/mcp-vulnerability-scanner | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Version | 0.4.1 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Package registries | npm | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Repository | https://github.com/GuardBee/guardbee-mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
- VERSION30 Oct 20260.4.0 → 0.4.1
- VERSION30 Oct 20260.3.2 → 0.4.0
- VERSION26 Oct 20260.2.4 → 0.3.2
- VERSION26 Oct 20260.3.2 → 0.2.4
- VERSION22 Oct 20260.3.1 → 0.3.2
- VERSION22 Oct 20260.3.0 → 0.3.1
- VERSION22 Oct 20260.2.5 → 0.3.0
- VERSION19 Oct 20260.2.4 → 0.2.5
- VERSION19 Oct 20260.2.5 → 0.2.4
- VERSION13 Oct 20260.2.4 → 0.2.5
- NEW28 Sept 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is vulnerability-scanner still online?
Free alerts · no account▲ 0Do you publish vulnerability-scanner? Get it seen by people choosing a tool
For publishers · optionalLaunch Spotlight: 60 days of clearly labelled Sponsored visibility on the use-case pages where vulnerability-scanner already appears, plus the weekly Pulse. No click in 60 days? The next 60 days are free.
Sponsored placements never change a score or a rank.
Questions about vulnerability-scanner
How do I connect vulnerability-scanner?
Install the npm package @guardbee/mcp-vulnerability-scanner. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What can I use vulnerability-scanner for?
Based on its description, it is most relevant to: scan code for vulnerabilities, review pull requests.