Bring Application Security
to Cursor
Learn how to connect HCL AppScan to Cursor and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for Subscribers
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 Cursor?
Cursor's Agent mode turns HCL AppScan into an in-editor superpower. Ask Cursor to generate code using live data from HCL AppScan and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
HCL AppScan in Cursor
HCL AppScan and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect HCL AppScan to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.