Can the AI forcefully block attackers or does it just view them?

You can explicitly instruct the AI to use the `block_attacker` tool, 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` tool 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.

Salt Security MCP Server for Claude Desktop 10 tools — connect in under 2 minutes

Name: Salt Security
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 10 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Salt Security and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "salt-security": {
      // Your Vinkius token — get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Salt Security MCP Server

Connect your AI directly with Salt Security to proactively defend your Application Programming Interface (API) environment. Improve API discovery, manage security posture, and remediate threats in real-time through simple conversational prompts.

Claude Desktop is the definitive way to connect Salt Security to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

API Inventory & Discovery — View all auto-discovered APIs in your environment, including unknown or shadow APIs (get_inventory). Retrieve schema details, identify exposed sensitive data (PII), and analyze structural drifts (get_endpoint).
Threat Intelligence & Monitoring — Monitor active API attacks and business logic abuses as they happen (get_attacks). Profile known threat actors to uncover behavioral patterns (get_attackers).
Active Remediation — Respond to incidents immediately by triggering blockade commands against attackers, seamlessly passing instructions to your integrated WAFs (block_attacker).
Posture & Governance Assessment — Identify design flaws and vulnerabilities before they reach production (get_posture_vulnerabilities). Manage OpenAPI (OAS) specifications (list_oas_specs, upload_oas_spec) and verify active governance rules (get_governance_policies).

The Salt Security MCP Server exposes 10 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Salt Security to Claude Desktop via MCP

Follow these steps to integrate the Salt Security MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Salt Security

Look for the 🔌 icon in the chat — your 10 tools are now available

Why Use Claude Desktop with the Salt Security MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Salt Security through the Model Context Protocol.

Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network

Salt Security + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Salt Security MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Salt Security MCP Tools for Claude Desktop (10)

These 10 tools become available when you connect Salt Security to Claude Desktop via MCP:

block_attacker

Issues a command to block a specific attacker

get_attackers

Lists known threat actors profiled by Salt

get_attacks

Lists detected malicious API attacks

get_endpoint

Retrieves details for a specific API endpoint

get_governance_policies

Lists active API governance rules

get_inventory

Retrieves the auto-discovered API inventory

get_posture_vulnerabilities

Retrieves identified pre-production design flaws

get_system_health

Checks the health of traffic mirror ingestion

list_oas_specs

Lists all uploaded OpenAPI specifications

upload_oas_spec

Uploads a new OAS/Swagger specification

Example Prompts for Salt Security in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Salt Security immediately.

"List all auto-discovered APIs including shadow and zombie APIs in our infrastructure."

"Are we facing any recent attacks aimed at business logic?"

"Block attacker 'ATT-992' immediately."

Troubleshooting Salt Security MCP Server with Claude Desktop

Common issues when connecting Salt Security to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting — wait a few seconds.

Salt Security + Claude Desktop FAQ

Common questions about integrating Salt Security MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully — if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL — Claude auto-negotiates the transport protocol.