io.github.4hmetuyar/vulnerability-scanner
guardbee-vulnerability-scanner
Is the io.github.4hmetuyar/vulnerability-scanner MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-27.
Triggers GuardBee scans, queries findings, AI-assisted remediation guidance
alive probed 2026-11-15 · unchanged since 2026-10-27
- Run it
- npx -y @guardbee/mcp-vulnerability-scanner@0.2.4 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- guardbee-vulnerability-scanner 0.1.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- 0.1 % of a 1M context window
- Count
- 1.2k tokens in Claude Opus 5.5, exact, measured 2026-10-27. With the Claude Code prefix mcp__…__ on each tool name: 1.3k. The o200k_base estimate is 668. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/GuardBee/guardbee-mcp
- Registry
- active, updated 2026-09-28 · registry entry
- Changes
- 2 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.82×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| start_scan | 339 | 186 | 28 % |
| get_findings | 306 | 168 | 25 % |
| list_scans | 240 | 132 | 20 % |
| scan_and_report | 206 | 113 | 17 % |
| get_scan_status | 126 | 69 | 10 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.4hmetuyar/tool-poisoning-scanner · alive
- io.github.4hmetuyar/toxic-flow-auditor · alive
- io.github.4hmetuyar/unbounded-consumption-auditor · alive
- io.github.4hmetuyar/vector-store-scanner · alive
- io.github.5dive-ai/5dive-mcp · alive
- JobGPT - Job Search Automation & Auto Apply io.github.6figr-com/jobgpt-mcp-server · alive
- agent-sec-scan io.github.6mickswagger9/agent-sec-scan · alive
- compute-api-mcp io.github.6mickswagger9/compute-api-mcp · crashed on start
Servers that mention vulnerability.
- CERT-FR Security Advisories — buy per-query in-session (certfrwatch) com.a2awire/data-cert-fr-advisory-national-cert-alert · alive
- CISA Known Exploited Vulnerabilities (kevwatch) com.a2awire/data-cisa-known-exploited-vulnerability-catalog · alive
- CVE Security Advisories (NVD High & Critical) — buy per-query in-session (cvewatch) com.a2awire/data-cve-security-advisory-vulnerability-database · alive
- Dependency Vulnerability Tracker — package security advisories ($0.01/query) com.a2awire/data-dependency-vulnerability-malicious-package-security · alive
- Go Vulnerability Database Tracker — buy per-query in-session (govulnwatch) com.a2awire/data-go-vulnerability-golang-security · alive
- Rust Crate Security Advisories — buy per-query in-session (rustsecwatch) com.a2awire/data-rust-security-crate-vulnerability · alive
- Ubuntu Security Notices / USN (usnwatch) — buy per-query in-session com.a2awire/data-ubuntu-security-linux-vulnerability · alive
- CVElens Vulnerability Intelligence com.cvelens/cvelens · TLS error
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-27 06:52 | alive | 305 ms | 5 | 1.2k | 668 |
| 2026-10-20 06:40 | alive | 255 ms | 5 | 668 |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers initialize and tools/list. Nothing to fix.