Vulnify
Ask Vulnify before an AI agent acts: get ALLOW, REVIEW or BLOCK for a proposed action, and read and test your organization's policies.
- Brand
- Unknown
- Category
- Pending
- Primary Subcategory
- Pending
Integration details
Description
Vulnify is a runtime authorization layer for AI agents. Before an agent reads, writes, deletes, exports or sends data, it describes the action and Vulnify returns ALLOW, REVIEW or BLOCK based on your organization's policies, a risk score and a sensitive-data scan. A REVIEW waits for a person on your team to approve or deny it in Vulnify or Slack. This connector lets Claude ask those questions on your behalf: - Check action: dry-run one action against your stored policies. Records nothing. - Decide action: record a real decision. It writes a security event and an audit entry and may open a human review. - Get decision: read a recorded decision, optionally waiting up to 30 seconds for a pending review to resolve. - List policies: read your policies as code. - Test policies: evaluate up to 200 test cases against stored or proposed policies without saving anything. What it cannot do, on purpose: there is no approve or deny tool, so a REVIEW can only be resolved by a person in Vulnify. It cannot create, change or delete policies, and it does not run or forward the actions it checks. You sign in with your Vulnify account (OAuth 2.1). The consent screen lists each permission, and you can revoke access at any time on the Connected apps page in Vulnify. Optional text you send for scanning is processed in memory and not stored. Requires a Vulnify account (vulnify.io). Docs: https://docs.vulnify.io/mcp/
- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Category
- Pending
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- Unknown
- Access
- Account required
- First tracked
- 2026-10-10
- Tool count
- 5
- Geography
- US
The broad Category that contains the Primary Subcategory.
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Connector discovery is coming soon
Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What discovery looks like

Claude can surface verified Connectors when they match a user’s Prompt.
How Claude Connector discovery works
Your Connector will compete to appear for users’ Prompts once Claude verifies it
Competitive lineup
5 tools agents can invoke
Vulnify Claude Connector FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve Vulnify's Claude Connector discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.