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.

HCL AppScan MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: HCL AppScan
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to HCL AppScan through Vinkius, pass the Edge URL in the `mcps` parameter and every HCL AppScan tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

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.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="HCL AppScan Specialist",
    goal="Help users interact with HCL AppScan effectively",
    backstory=(
        "You are an expert at leveraging HCL AppScan tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in HCL AppScan "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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 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).

When paired with CrewAI, HCL AppScan becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call HCL AppScan tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

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.

The HCL AppScan MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI 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 HCL AppScan to CrewAI via MCP

Follow these steps to integrate the HCL AppScan MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from HCL AppScan

Why Use CrewAI with the HCL AppScan MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with HCL AppScan through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

HCL AppScan + CrewAI Use Cases

Practical scenarios where CrewAI combined with the HCL AppScan MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries HCL AppScan for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries HCL AppScan, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain HCL AppScan tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries HCL AppScan against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

HCL AppScan MCP Tools for CrewAI (10)

These 10 tools become available when you connect HCL AppScan to CrewAI via MCP:

get_account_check

Verify AppScan account connection

get_account_info

Retrieve authenticated user information

get_app

Get details for a specific application

get_issue

Get detailed information about a specific vulnerability

get_scan

Get details and status for a specific scan

list_apps

List all applications in your AppScan inventory

list_issues

List vulnerabilities found for a specific application

list_presence

List AppScan Presences (local agents)

list_scans

List all scans performed in the account

start_dast_scan

Start a new Dynamic Analysis (DAST) scan

Example Prompts for HCL AppScan in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with HCL AppScan immediately.

"List all applications in my AppScan inventory."

"Show me high severity issues for application 'Customer Portal'."

"Start a new DAST scan for appId '12345' with URL 'https://portal.example.com'."

Troubleshooting HCL AppScan MCP Server with CrewAI

Common issues when connecting HCL AppScan to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

HCL AppScan + CrewAI FAQ

Common questions about integrating HCL AppScan MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.