Vulnify
io.vulnify/mcp
About Vulnify
Vulnify is an MCP server published by vulnify.io. Ask Vulnify before an AI agent acts. Check, record, and read policy decisions.
It runs on your own machine: your AI client starts it from the npm package @vulnify/mcp at version 0.1.4, or you can connect to the hosted version instead.
It asks for one secret: VULNIFY_API_KEY. Give it a key with the least access that still works.
Version 0.1.4 was published on 12 October 2026, and the source code is public, so you can read it before installing.
Written from the registry entry. 10 automated checks on the registry entry and the package code: 8 pass, 0 warn, 0 fail, 2 info. How we check.
What it asks for
| Variable | Required | Secret | Description |
|---|---|---|---|
VULNIFY_API_KEY | Yes | Yes | Vulnify API key (vln_live_... or vln_test_...) for the local stdio process. The hosted server signs in with Vulnify and does not need this variable. |
VULNIFY_BASE_URL | No | No | API base URL. Defaults to https://api.vulnify.io. |
Checks
| Check | Result | Detail |
|---|---|---|
| Source repository linked | Pass | https://github.com/vulnify/vulnify-mcp |
| Version pinned | Pass | Every package has an explicit version |
| Remote uses HTTPS | Pass | All remote endpoints use https:// |
| Secrets requested | Info | Asks for 1 secret: VULNIFY_API_KEY |
| Known package registry | Pass | All packages come from npm, PyPI, OCI, NuGet or MCPB |
| Namespace ownership | Info | Name verified via domain vulnify.io |
| Registry text aimed at the AI | Pass | Description and settings contain no hidden characters or instructions to the AI |
| Install scripts | Pass | @vulnify/mcp@0.1.4 runs nothing at install |
| Code red flags | Pass | Read 6 files in @vulnify/mcp@0.1.4: 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 6 files, including comments and the README |
Popularity & health: 53 / 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, 9 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.vulnify/mcp |
|---|---|
| Publisher | Domain vulnify.io |
| How the name is verified | Name verified via domain vulnify.io. The registry ties the name prefix to that account or domain; it does not check the code. |
| Type | Local package and a hosted remote |
| Packages | npm @vulnify/mcp 0.1.4 (stdio) |
| Remote endpoints | streamable-http https://mcp.vulnify.io/mcp |
| Version | 0.1.4 |
| Published | |
| Last updated | |
| Source repository | https://github.com/vulnify/vulnify-mcp |
| Website | https://docs.vulnify.io |
| Category | Agent safety & governance (assigned by keyword rule, not by hand) |
Related servers in Agent safety & governance
- VERAX7/7The body an agent asks before it acts: decide, approve, and keep a…
- Quirna7/7Ask a human before your agent acts: approval requests decided on a…
- Syl Guardian4/4Causal guardrail: pass/caution/hold verdict on a causal claim…
- Kaval7/7Verify the facts an agent's action depends on before it acts —…
- scrapecheck4/4Verify before your agent acts on data it paid for. Signed verdicts,…
- Kaval7/7Verify the facts an agent's action depends on before it acts —…