Ask Vulnify before an AI agent acts. Check, record, and read policy decisions.
Connect Remote server
claude mcp add --transport http mcp https://mcp.vulnify.io/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"mcp": {
"url": "https://mcp.vulnify.io/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"mcp": {
"type": "http",
"url": "https://mcp.vulnify.io/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://mcp.vulnify.io/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server asks for a key before it lists its tools. Connect it with your own key to see them.
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | 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. |
Details
| Endpoint | https://mcp.vulnify.io/mcp (Streamable HTTP) |
| Package | @vulnify/[email protected] (NPM, stdio) |
| First published | 12 Oct 2026 |
| Last updated | 12 Oct 2026 |
| Registry name | io.vulnify/mcp |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
