Bring Application Security
to Claude Desktop
Learn how to connect HCL AppScan to Claude Desktop and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the HCL AppScan MCP Server?
The HCL AppScan MCP Server brings powerful application security testing capabilities directly to your AI agent. Seamlessly manage your security posture by monitoring vulnerabilities, tracking scan progress, and auditing your application inventory across HCL AppScan on Cloud (ASoC).
Key Features
- Inventory Management — List and search for applications in your security inventory to find their unique IDs.
- Vulnerability Tracking — Retrieve detailed lists of security issues found during scans, including severity and status.
- Scan Oversight — Monitor all performed scans and check the real-time status of active security tests.
- Dynamic Analysis (DAST) — Start new DAST scans for your web applications directly from your chat interface.
- Agent & Presence Monitoring — List available Presences (local agents) used for scanning internal applications.
- Real-time Insights — Get instant summaries of your security findings and prioritize remediation efforts.
Who is this for?
- Security Engineers — Quickly audit security findings across multiple applications without manual dashboard exports.
- DevSecOps Teams — Integrate security scan monitoring and initiation into your automated workflows.
- Compliance Officers — Monitor application security status and ensure all apps are regularly scanned.
Built-in capabilities (10)
Verify AppScan account connection
Retrieve authenticated user information
Get details for a specific application
Get detailed information about a specific vulnerability
Get details and status for a specific scan
List all applications in your AppScan inventory
List vulnerabilities found for a specific application
List AppScan Presences (local agents)
List all scans performed in the account
Start a new Dynamic Analysis (DAST) scan
Why Claude Desktop?
Claude Desktop is the definitive way to connect HCL AppScan to your AI workflow. Add 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.
- —
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 Vinkius Edge network
HCL AppScan in Claude Desktop
HCL AppScan and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect HCL AppScan to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for HCL AppScan in Claude Desktop
The HCL AppScan 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. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* 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
How Vinkius secures
HCL AppScan for Claude Desktop
Every tool call from Claude Desktop to the HCL AppScan MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I get my AppScan API Key ID and Secret?
Log in to the AppScan on Cloud console, go to your User Profile (top right), and select API Keys. You can generate a new Key ID and Key Secret there.
Does this server support the EU region?
Yes, you can configure the APPSCAN_REGION environment variable to eu to connect to the European data center (eu.cloud.appscan.com).
Can I start a scan for an internal application?
Yes, provided you have an AppScan Presence (local agent) configured. You can use the list_presence tool to check their availability before starting a scan.
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.
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.
