vuln-check
io.github.ciloops/vuln-check
About vuln-check
vuln-check is an MCP server published by the GitHub account ciloops. Local vulnerability scan on top of grype, with prioritised upgrade actions for agents.
It runs on your own machine: your AI client starts it from the npm package @ciloops/vuln-check at version 0.1.3.
It asks for no keys or passwords.
Version 0.1.3 was published on 23 October 2026, and the source code is public, so you can read it before installing.
Written from the registry entry. 9 automated checks on the registry entry and the package code: 6 pass, 1 warn, 0 fail, 2 info. How we check.
What it asks for
This server declares no environment variables, so it asks for no keys or settings.
Checks
| Check | Result | Detail |
|---|---|---|
| Source repository linked | Pass | https://github.com/ciloops/vuln-check |
| Version pinned | Pass | Every package has an explicit version |
| Secrets requested | Info | Asks for no secrets |
| Known package registry | Pass | All packages come from npm, PyPI, OCI, NuGet or MCPB |
| Namespace ownership | Info | Name verified via GitHub account ciloops |
| Registry text aimed at the AI | Pass | Description and settings contain no hidden characters or instructions to the AI |
| Install scripts | Warn | Runs at install: postinstall: node install.js |
| Code red flags | Pass | Read 4 files in @ciloops/vuln-check@0.1.3: no obfuscation, encoded execution, credential reads or data-collection endpoints found |
| Text aimed at the AI | Pass | No hidden characters or instructions to the AI in 4 files, including comments and the README |
Popularity & health: 55 / 100
Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.
0 forks, 0 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.
What people say
No Hacker News threads link to its source code.
Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.
Facts
| Registry name | io.github.ciloops/vuln-check |
|---|---|
| Publisher | GitHub account ciloops |
| How the name is verified | Name verified via GitHub account ciloops. The registry ties the name prefix to that account or domain; it does not check the code. |
| Type | Local: runs on your machine from a package |
| Packages | npm @ciloops/vuln-check 0.1.3 (stdio)oci ghcr.io/ciloops/vuln-check:0.1.3 no version given (stdio) |
| Version | 0.1.3 |
| Published | |
| Last updated | |
| Source repository | https://github.com/ciloops/vuln-check |
| Website | None linked |
| Category | Security (assigned by keyword rule, not by hand) |
Related servers in Security
Cork MCP4/4Every Cork API operation, plus cross-client risk attribution and…- vuln-triage-mcp7/7Tells your AI agent which vulnerabilities to fix first, using…
- vuln-intel4/4Free hosted CVE intel for bug-bounty agents: CVE fact-check, attack…
- Kestrova: Solidity Vulnerability Scan4/4Solidity smart contract vulnerability scan (Slither) for AI agents.…
- owasp-scan7/7Unified OWASP MCP Top 10 scan — path or live tools/list, A–F grade,…
- mcp-scan5/7Passive security scanner: audits MCP servers against the OWASP MCP…