Vulnify

Name: Vulnify
Author: vulnify

by vulnifyversion 0.1.4i★ –iComputer or cloud

Registry nameio.vulnify/mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Other
You need to fill in: VULNIFY_API_KEY, Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: VULNIFY_API_KEY, VULNIFY_BASE_URL, Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

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

Or run it on your computer

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

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

VULNIFY_API_KEY secret required 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 secret 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.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain vulnify.io (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32558 servers in this category
Published to the registry more recently than 60% of the other 32558 servers in this category
Basic checks equal to or better than 100% of the other 32558 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Vulnify safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: VULNIFY_API_KEY, Authorization

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.4) reached the registry 26 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, FactLot

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

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

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

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

Runs in the cloud★ 211Updated yesterday

Install

FactLot

by 9mp96ygnbk-alt

Cited CRE facts and deterministic calculators for agents: rent, CAM, debt sizing, IRR, parcel IDs.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

Only the beginning is shown; read the rest in the repo

Vulnify

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

FactLot

README from the maker

Quickstart

Sign in with Vulnify

Claude

Cursor

Grok

Claude Code

API key or local npx

How it works

Tools

Safety

OAuth scopes