Vulnify

Name: Vulnify
Author: vulnify

作者：vulnify版本 0.1.4i★ –i电脑或云端

注册名称io.vulnify/mcp

安装

概览

作者提供的说明（英文原文）

Ask Vulnify before an AI agent acts. Check, record, and read policy decisions.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 电脑或云端
传输方式: stdio, Streamable HTTP
分类: 其他
你需要填写：VULNIFY_API_KEY, Authorization

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
需要你自己填写： VULNIFY_API_KEY, VULNIFY_BASE_URL, Authorization

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

在云端运行无需安装任何东西，通过互联网连接
npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

或者在你的电脑上运行

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "vulnify": {
      "command": "npx",
      "args": [
        "-y",
        "@vulnify/mcp"
      ],
      "env": {
        "VULNIFY_API_KEY": "your-value",
        "VULNIFY_BASE_URL": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add --transport http vulnify https://mcp.vulnify.io/mcp --header 'Authorization: Bearer {api_key}'

或者在你的电脑上运行

claude mcp add vulnify --env VULNIFY_API_KEY=your-value --env VULNIFY_BASE_URL=your-value -- npx -y @vulnify/mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "vulnify": {
      "url": "https://mcp.vulnify.io/mcp",
      "headers": {
        "Authorization": "Bearer {api_key}"
      }
    }
  }
}

或者在你的电脑上运行

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "vulnify": {
      "command": "npx",
      "args": [
        "-y",
        "@vulnify/mcp"
      ],
      "env": {
        "VULNIFY_API_KEY": "your-value",
        "VULNIFY_BASE_URL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "vulnify": {
      "type": "http",
      "url": "https://mcp.vulnify.io/mcp",
      "headers": {
        "Authorization": "Bearer {api_key}"
      }
    }
  }
}

或者在你的电脑上运行

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "vulnify": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@vulnify/mcp"
      ],
      "env": {
        "VULNIFY_API_KEY": "your-value",
        "VULNIFY_BASE_URL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

VULNIFY_API_KEY 机密必填 env
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 env
API base URL. Defaults to https://api.vulnify.io.
Authorization 机密 HTTP header
Sign in with Vulnify (OAuth 2.1). Leave this header empty. Set it only to send an API key (vln_live_... or vln_test_...) as a Bearer token. X-Vulnify-Key also works.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过域名 vulnify.io 验证（注册中心会核实域名所有权）
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
… 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
… 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32497 个服务器的 0%
发布到注册中心的时间比此分类中其他 32497 个服务器的 60% 更新
基础检查结果等于或优于此分类中其他 32497 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Vulnify 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：VULNIFY_API_KEY, Authorization

它在我的电脑上运行还是在云端？

两种方式都可以：安装在你的电脑上，或者连接云端版本。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.4）于26天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Zoo MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新

安装

Zoo MCP

作者：KittyCAD

An MCP server that provides access to the Zoo API for various CAD operations and tools.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Vulnify MCP

Ask Vulnify before an AI agent reads, writes, deletes, exports, or sends data.

finalDecision is the authoritative result: ALLOW , REVIEW , or BLOCK .

Connect to Claude · Docs · MCP · Changelog · Node SDK

@vulnify/mcp is the MCP server for Vulnify, a runtime authorization layer for AI agents. The agent asks first. This process proxies https://api.vulnify.io. It does not store events or API keys.

Sign in with Vulnify (OAuth 2.1) at https://mcp.vulnify.io/mcp. That hosted server speaks stateless Streamable HTTP. The local path is npx -y @vulnify/mcp with VULNIFY_API_KEY.

check_action is a dry run. It skips the PII scan and records nothing. decide_action records a real decision. A REVIEW waits for a person. This server cannot approve or deny one.

Application code that should decide inside your own process uses the Node SDK (@vulnify/sdk). This package does not depend on the SDK. The SDK turns some transport failures into a fail-closed decision. This server returns those failures as MCP tool errors, so a model does not read them as ALLOW.

Quickstart

The source of truth is docs.vulnify.io/mcp. The same steps are in docs/clients.md.

Sign in with Vulnify

Connect to https://mcp.vulnify.io/mcp. Leave API-key and OAuth client fields empty. The client receives HTTP 401 and:

WWW-Authenticate: Bearer realm="https://mcp.vulnify.io/mcp", resource_metadata="https://mcp.vulnify.io/.well-known/oauth-protected-resource/mcp", scope="decisions:read decisions:write policies:read policies:test"

The body is {"error":"unauthorized","message":"Sign in with Vulnify, or send an API key as Authorization: Bearer or X-Vulnify-Key:."}. Protected-resource metadata lists the authorization server https://api.vulnify.io.

You choose an organization and allow the scopes the client requests:

Scope	Tools
`decisions:read`	`get_decision`
`decisions:write`	`decide_action`
`policies:read`	`list_policies`
`policies:test`	`check_action`, `test_policies`

After you allow access, the hosted server offers those five tools. plan_policy_changes and check_mcp_tool_call are not in that list. They need an API key. A missing scope comes back as a tool error that names the scope. That error is not an ALLOW. Revoke the connection under Settings > Connected apps: app.vulnify.io/settings/connected-apps.

Claude

Vulnify is available in Claude's connector directory: [Connect to Claude](https://claude.ai/directory/vulnify). Select Connect on the listing, then sign in with Vulnify. Walkthrough: human approval for Claude actions.

To add it by URL instead, open Settings > Connectors > Add custom connector. Set the URL to https://mcp.vulnify.io/mcp. Do not paste an API key. Add Vulnify in Claude opens that dialog with the name and URL filled in. Claude then starts Sign in with Vulnify.

Cursor

Install in Cursor adds the hosted server and starts sign-in.

The same server in .cursor/mcp.json, or in ~/.cursor/mcp.json, is the URL with no header:

"mcpServers": { "vulnify": { "url": "https://mcp.vulnify.io/mcp" } } }

Grok

Open grok.com/connectors, then New Connector > Custom. Name it Vulnify. Set the URL to https://mcp.vulnify.io/mcp. Leave the OAuth fields empty. Grok starts Sign in with Vulnify.

Claude Code

Add the Vulnify marketplace, then install the plugin. It connects to https://mcp.vulnify.io/mcp and signs in with Vulnify. A PreToolUse hook checks risky tool calls before they run. Claude Code asks for an API key for that hook when you enable the plugin. The hosted tools still use sign-in, not that key.

claude plugin marketplace add vulnify/vulnify-mcp

claude plugin install vulnify@vulnify-mcp

Inside a session:

/plugin marketplace add vulnify/vulnify-mcp

/plugin install vulnify@vulnify-mcp

To add only the hosted server, without the hook:

claude mcp add --transport http vulnify https://mcp.vulnify.io/mcp

Claude Code then signs in. Do not pass an API key on this command.

API key or local npx

Use an API key when you need plan_policy_changes or check_mcp_tool_call, when the client cannot open a browser, or when the key has an IP allowlist. The local process needs Node.js 20 or newer and reads VULNIFY_API_KEY. It does not open the OAuth consent page.

npx -y @vulnify/mcp

VULNIFY_API_KEY=vln_live_... npx -y @vulnify/mcp

The key is vln_live_... or vln_test_.... A TEST key stores sandbox events. Those stay out of the main dashboards.

On the hosted server, both headers still work. Send the key on every request:

Authorization: Bearer <key>

X-Vulnify-Key:

An API-key session lists all seven tools.

Cursor, hosted:

"mcpServers": { "vulnify": { "url": "https://mcp.vulnify.io/mcp", "headers": { "Authorization": "Bearer vln_live_..." } } } }

Cursor, local:

"mcpServers": { "vulnify": { "command": "npx", "args": ["-y", "@vulnify/mcp"], "env": { "VULNIFY_API_KEY": "vln_live_..." } } } }

X-Vulnify-Key works in place of Authorization on the hosted server.

Claude Code with an API key:

claude mcp add --transport http vulnify https://mcp.vulnify.io/mcp --header "Authorization: Bearer vln_test_your_key"

Prefer an environment variable over a key written into the shell history. For sign-in, use the Claude Code command with no header. The plugin hook asks for its own API key when you enable it. Do not put that key on claude mcp add.

Claude Desktop can run the local process. On macOS the file is ~/Library/Application Support/Claude/claude_desktop_config.json. On Windows it is %APPDATA%\Claude\claude_desktop_config.json. Restart the app after saving.

"mcpServers": { "vulnify": { "command": "npx", "args": ["-y", "@vulnify/mcp"], "env": { "VULNIFY_API_KEY": "vln_live_..." } } } }

VS Code, .vscode/mcp.json, hosted:

"servers": { "vulnify": { "type": "http", "url": "https://mcp.vulnify.io/mcp", "headers": { "Authorization": "Bearer ${input:vulnify-api-key}" } } } }

VS Code, local:

"servers": { "vulnify": { "type": "stdio", "command": "npx", "args": ["-y", "@vulnify/mcp"], "env": { "VULNIFY_API_KEY": "${input:vulnify-api-key}" } } } }

How it works

The finalDecision field is the authoritative result. A tool error is not an ALLOW.

Tools

Every tool has a title and readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. Hints tell the client how to present the tool. They do not change what the tool does.

Tool	API	Records?	readOnlyHint	Notes
`check_action`	`POST /v1/policies/test` (one case)	No	true	Skips the PII scan and records nothing. No event id.
`decide_action`	`POST /v1/events`	Yes	false	Writes a security event and an audit entry. `finalDecision` is the authoritative result.
`get_decision`	`GET /v1/events/{id}`	No	true	Reads a decision. Optional wait polls a `REVIEW` until `ALLOW` or `BLOCK` (30 seconds max).
`list_policies`	`GET /v1/policies`	No	true	Policies as code, sorted by name.
`test_policies`	`POST /v1/policies/test`	No	true	Up to 200 cases. Skips the PII scan. Proposed `policies` are not saved.
`plan_policy_changes`	`POST /v1/policies/apply`	No	true	`dryRun` is forced to true. Needs an org-wide LIVE key.
`check_mcp_tool_call`	`POST /v1/gateway/mcp`	Yes	false	Maps a tool name to an action and records the decision. Does not run the tool.

destructiveHint is false on every tool. openWorldHint is false on every tool, because each call stays inside the caller's own Vulnify organization. idempotentHint is true for the read-only tools and false for decide_action and check_mcp_tool_call. An idempotencyKey makes a retry of a recorded decision return the same event.

Policy list, test, and plan calls are limited to 60 requests per minute per key. Batch dry runs with test_policies. POST /v1/events has its own limit. The OpenAPI text says only that the limit was exceeded.

Safety

This server cannot change a review and cannot save a policy.

There is no approve tool and no deny tool. A human resolves a REVIEW in Vulnify.
There is no apply tool. plan_policy_changes calls POST /v1/policies/apply with dryRun: true on every request. The tool input has no dryRun field. The server sets dryRun last, so a caller cannot turn the dry run off. The tool returns the diff.
POST /v1/gateway/http is not a tool. On ALLOW, that API endpoint forwards the HTTP call. This server does not.

plan_policy_changes needs an org-wide LIVE key. A TEST key or an agent-bound key gets 403. An OAuth session does not list plan_policy_changes or check_mcp_tool_call.

OAuth scopes

User login is the hosted HTTP server. The local stdio process still uses an API key. The hosted server maps tools to scopes:

Tool	Scope	OAuth route
`check_action`	`policies:test`	`POST /v1/mcp/policies/test`
`test_policies`	`policies:test`	`POST /v1/mcp/policies/test`
`decide_action`	`decisions:write`	`POST /v1/mcp/events`
`get_decision`	`decisions:read`	`GET /v1/mcp/events/{id}`
`list_policies`	`policies:read`	`GET /v1/mcp/policies`
`plan_policy_changes`	API key and stdio only

只显示了开头部分；其余内容请在仓库中阅读

Vulnify

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

或者在你的电脑上运行

或者在你的电脑上运行

或者在你的电脑上运行

或者在你的电脑上运行

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

Zoo MCP

作者的 README

Quickstart

Sign in with Vulnify

Claude

Cursor

Grok

Claude Code

API key or local npx

How it works

Tools

Safety

OAuth scopes