Salt Security Connector for AI agents.
10 live capabilities
Defend your API environment and block active threats in real-time.
Waiting for input…
Why people use Salt Security
Salt Security API Threat Detection
With this Connector, you can stop the tab-hopping. You can ask your agent to identify the behavior of a threat actor and trigger a blockade against them immediately. You get the same intelligence as your security console, but through a single conversational prompt.
What Vinkius changes
You get a conversational interface for your entire API security stack.
Use it from Claude, ChatGPT, Cursor or another AI client you already have.
One account · 5,900+ Connectors
- Real-world use case 01
Stopping a live attack
A security analyst sees a spike and asks the agent to check for malicious activity.
- Real-world use case 02
Auditing shadow APIs
A developer wants to see what's currently live.
- Real-world use case 03
Checking for PII leaks
During a security audit, a user asks the agent to check for PII leaks.
Complete set · 10capabilities
The complete Salt Security capability set.
These are the exact actions your AI can choose when you ask it to work with Salt Security.
01—04
4 capabilities in this set.
Part of 10 available through Salt Security.
- 01 Capability
Get attackers
Lists known threat actors profiled by the platform. Use this to see behavioral patterns of attackers.
- 02 Capability
Get attacks
Lists detected malicious API attacks. This helps you monitor real-time threats and business logic abuse.
- 03 Capability
Get endpoint
Retrieves the specific details and schema for a single API endpoint. Use this to check for PII exposure.
- 04 Capability
Get governance policies
Lists the active rules governing your API environment. This helps you verify your current security posture.
05—07
3 capabilities in this set.
Part of 10 available through Salt Security.
- 05 Capability
Get inventory
Pulls a full list of every API your system has auto-discovered. It is the best way to find shadow APIs.
- 06 Capability
Get posture vulnerabilities
Identifies design flaws and security gaps before they go live. Use this to catch issues during development.
- 07 Capability
List oas specs
Lists all the OpenAPI specifications you have uploaded. Use this to audit your existing documentation.
08—10
3 capabilities in this set.
Part of 10 available through Salt Security.
- 08 Capability
Upload oas spec
Uploads a new Swagger or OpenAPI file to the console. This keeps your security specs up to date.
- 09 Capability
Block attacker
Issues a command to block a specific threat actor. This provides immediate remediation for active attacks.
- 10 Capability
Get system health
Checks if your traffic mirror ingestion is running correctly. This ensures you have constant visibility.
Set up in minutes
One URL. Then ask Salt Security to work.
Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Salt Security from the conversation.
Choose your client
Live previewAdvanced clients IDE · CLI
Claude · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_HEqpwxZCJGloy9SZRikbBjYA9GqrD7wwt82MwMIn/mcp - Step 01
Open Connectors
In Claude Web or Claude Desktop, open Settings and choose Connectors.
- Step 02
Add the URL
Choose Add custom connector, name it Salt Security, and paste the URL above.
- Step 03
Turn it on in chat
Select +, open Connectors, and enable Salt Security for the conversation.
ChatGPT · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_HEqpwxZCJGloy9SZRikbBjYA9GqrD7wwt82MwMIn/mcp - Step 01
Open MCP settings
On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
- Step 02
Add the URL
Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the Salt Security URL.
- Step 03
Save and start
Save the connection and enable Salt Security in your conversation. Desktop may ask you to restart once.
Cursor · IDE configuration
Advanced setup
{
"mcpServers": {
"salt-security": {
"url": "https://edge.vinkius.com/vk_preview_HEqpwxZCJGloy9SZRikbBjYA9GqrD7wwt82MwMIn/mcp"
}
}
}- Step 01
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
- Step 02
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
- Step 03
Save the file
Cursor will automatically detect the new Connector
- Step 04
Start using Salt Security
Open Agent mode in chat and ask: "Using Salt Security, help me...". 10 tools available
VS Code Copilot · IDE configuration
Advanced setup
{
"mcpServers": {
"salt-security": {
"url": "https://edge.vinkius.com/vk_preview_HEqpwxZCJGloy9SZRikbBjYA9GqrD7wwt82MwMIn/mcp"
}
}
}- Step 01
Create MCP config
Create a .vscode/mcp.json file in your project root
- Step 02
Add the server config
Paste the JSON configuration above
- Step 03
Enable Agent mode
Open GitHub Copilot Chat and switch to Agent mode using the dropdown
- Step 04
Start using Salt Security
Ask Copilot: "Using Salt Security, help me...". 10 tools available
Windsurf · IDE configuration
Advanced setup
{
"mcpServers": {
"salt-security": {
"url": "https://edge.vinkius.com/vk_preview_HEqpwxZCJGloy9SZRikbBjYA9GqrD7wwt82MwMIn/mcp"
}
}
}- Step 01
Open MCP Settings
Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
- Step 02
Add the server
Paste the JSON configuration above into mcp_config.json
- Step 03
Save and reload
Windsurf will detect the new server automatically
- Step 04
Start using Salt Security
Open Cascade and ask: "Using Salt Security, help me...". 10 tools available
Cline · IDE configuration
Advanced setup
{
"mcpServers": {
"salt-security": {
"url": "https://edge.vinkius.com/vk_preview_HEqpwxZCJGloy9SZRikbBjYA9GqrD7wwt82MwMIn/mcp"
}
}
}- Step 01
Open Cline MCP Settings
Click the Connectors icon in the Cline sidebar panel
- Step 02
Add remote server
Click "Add Connector" and paste the configuration above
- Step 03
Enable the server
Toggle the server switch to ON
- Step 04
Start using Salt Security
Ask Cline: "Using Salt Security, help me...". 10 tools available
Claude Code · Terminal command
Advanced setup
claude mcp add salt-security --transport http "https://edge.vinkius.com/vk_preview_HEqpwxZCJGloy9SZRikbBjYA9GqrD7wwt82MwMIn/mcp"- Step 01
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
- Step 02
Add the Connector
Run the command above in your terminal
- Step 03
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
- Step 04
Start using Salt Security
Ask Claude: "Using Salt Security, show me...". 10 tools are ready
Where the request belongs
Work Salt Security can move forward.
This is for security engineers and DevOps teams who are tired of manual dashboard hopping and need a faster way to identify and block API threats.
Security Engineer
Uses the Connector to quickly identify new shadow APIs and push block commands to the WAF during active incidents.
DevOps Engineer
Checks API posture and uploads new OpenAPI specs to ensure the production environment stays compliant.
SOC Analyst
Queries active attacks and threat actor profiles to prioritize incident response tasks.
API Product Manager
Uses the capability to get a complete inventory of all live endpoints to ensure documentation matches reality.
Build the capability set
Add more capabilities.
Each Connector adds new actions and data without changing how you work.
Browse ConnectorsHalo Security
Automate attack surface management via Halo Security. monitor assets, scans, and vulnerabilities directly from any AI agent.
Tenable
Manage Tenable Vulnerability Management scans, inspect cloud assets, and triage CVEs natively via your AI agent.
Intruder
Automate vulnerability scanning and security monitoring via Intruder.io API.
Trend Micro
Equip your AI agent with Vision One telemetry to investigate threats, audit endpoint activities, and manage security alerts natively.
Elastic Security
Manage SIEM and SOC operations via Elastic Security. monitor detection rules, search security alerts (Signals), handle whitelisting, and audit threat coverage directly from any AI agent.
UpGuard
Monitor your attack surface and assess vendor security risks with continuous scanning that identifies vulnerabilities before attackers do.
Bring your own AI
Change the model, client or framework. Keep Salt Security connected.
-
Claude -
ChatGPT -
Gemini -
Cursor -
VS Code -
Windsurf -
ZCode -
Cline -
Zed -
Continue -
Kiro -
Roo Code -
Zencoder -
Goose -
Void -
Augment Code -
Amp -
Qodo -
Tabnine -
Pieces -
Sourcegraph Cody -
JetBrains -
Warp -
Amazon Q -
Antigravity -
BoltAI -
Raycast -
Jan -
LM Studio -
AnythingLLM -
Open WebUI -
Msty -
Cherry Studio -
LibreChat -
TypingMind -
Chorus -
5ire -
n8n -
LangChain -
LlamaIndex -
CrewAI -
Vercel AI SDK
Before you connect
Questions about Salt Security.
The practical details behind the request, access and result.
How does Salt Security MCP help with shadow APIs?
It gives your AI the ability to see every API running in your environment, including those that aren't documented. This helps you find and secure 'shadow' APIs that could otherwise be left exposed.
Can I block attackers using my AI agent?
Yes. You can tell your agent to block a specific threat actor, and it will send that command to your security console to update your WAF rules immediately.
How do I find PII leaks in my APIs?
You can ask your agent to check specific endpoints for sensitive data exposure. It will analyze the schema and tell you if personal information is being leaked.
Can the AI help me manage my OpenAPI specs?
Yes, it can list your existing OpenAPI specifications and upload new ones. This helps you keep your security documentation in sync with your actual code.
Does this connect to my existing WAF?
The Connector works with Salt Security, which integrates with your existing WAF. This allows your agent to push blockade commands directly to your firewall.
What is business logic abuse in API security?
It refers to attacks that use valid API calls in malicious ways, like trying to bypass authentication or scrape data. This Connector helps detect those specific behaviors.
How does it handle my API governance?
It allows you to query and verify your active governance rules. You can use your agent to ensure that your security policies are being applied correctly across all APIs.
Can the AI forcefully block attackers or does it just view them?
You can explicitly instruct the AI to use the block_attacker capability, which triggers a remediation event across your security infrastructure (e.g., WAF integrations). It provides both visibility and direct active response.
Does Salt Security allow me to upload spec definitions (OAS) directly from my files via chat?
Yes, you can upload raw specification content using the upload_oas_spec capability for vulnerability testing and validation. Provide the exact OpenAPI content, and Salt will interpret it securely naturally properly successfully cleanly nicely properly natively completely optimally brightly cleanly beautifully actively quickly seamlessly efficiently correctly elegantly faithfully efficiently natively perfectly.
How frequently is the API inventory auto-discovered?
Salt maintains a continuous discovery architecture via passive traffic monitoring. This prevents any drift and immediately identifies 'Ghost APIs' when queried using the get_inventory capability.
One connection away
Give your agent a direct line to Salt Security.
Connect Salt Security once. Keep it beside 5,900+ managed Connectors when the next task needs more.
Explore every Connector No credit card required · Free tier available