Skip to main content
Glama
McxM123

acunetix-mcp-server

by McxM123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ACUNETIX_EMAILNoEmail for session login.
ACUNETIX_API_KEYNoOfficial API Key (recommended). Generate from your Acunetix profile.
ACUNETIX_BASE_URLNoBase URL of the Acunetix server.https://localhost:3443
ACUNETIX_PASSWORDNoPassword for session login.
ACUNETIX_VERIFY_SSLNoWhether to verify SSL certificate. Set to 'false' for self-signed certs.false

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
acunetix_loginA

【会话登录】登录 Acunetix 系统并建立会话（方式二）。

  • email/password 省略时使用环境变量 ACUNETIX_EMAIL / ACUNETIX_PASSWORD

  • 成功后 token 保存在内存中，后续工具自动携带认证

  • 注意：系统有单会话约束，会话登录会顶掉其他在线会话 提示：官方推荐方式是 acunetix_use_api_key（无单会话约束）。

acunetix_use_api_keyA

【官方推荐认证】使用 Profile 页生成的 API Key 认证（方式一）。

  • api_key: Profile 页 → API Key → Generate new API key 生成的 64 位密钥

  • 纯 X-Auth 头认证：REST 与 GraphQL 均可用，无需登录、无单会话约束

  • 若在环境变量 ACUNETIX_API_KEY 中配置，MCP server 启动时已自动启用，无需调用本工具

acunetix_logoutA

登出并清理本地会话。

acunetix_meB

获取当前登录用户信息（GraphQL）。

acunetix_gqlA

【通用 GraphQL 执行器】—— 大模型自主操作的核心通道。 向 /graphql/ 发送任意已确认可用的 query/mutation。

  • operation_name: 操作名（如 loginUser / getSharedUIData / getSystemInfo）

  • query: 完整 GraphQL 文本（依据官方文档与已知操作清单）

  • variables: 变量对象（可选） 注意：本系统 introspection 已禁用，必须使用已知操作名与字段结构。

acunetix_restB

【通用 REST 调用器】访问 /api/v1/* 端点。

  • method: GET/POST/PUT/DELETE/PATCH

  • path: 端点路径，如 targets / scans / vulnerabilities / reports / me

  • params: 查询参数（可选）

  • body: JSON 请求体（POST/PUT 等写操作需要） 高风险写操作请确保意图明确。

acunetix_list_targetsB

列出扫描目标（GET /api/v1/targets?l=N），含地址/ID/漏洞计数。

acunetix_get_targetA

获取单个目标详情（GET /api/v1/targets/{id}）。

acunetix_list_scansB

列出扫描任务（GET /api/v1/scans?l=N）。

acunetix_list_vulnerabilitiesB

列出漏洞（GET /api/v1/vulnerabilities?l=N）。

acunetix_list_reportsA

列出已生成报告（GET /api/v1/reports?l=N）。

acunetix_list_scan_profilesA

列出扫描配置（GET /api/v1/scanning_profiles），用于启动扫描时选 profile。

acunetix_statsA

当前用户统计（GET /api/v1/me/stats）：扫描/目标/漏洞汇总。

acunetix_add_targetA

【写操作】新增扫描目标（POST /api/v1/targets）。

  • address: 目标 URL/IP，如 http://example.com

  • criticality: 官方枚举 Critical[30]/High[20]/Normal[10]/Low[0]，默认 10；其他值报 400

acunetix_start_scanA

【写操作】对目标启动扫描（POST /api/v1/scans）。

  • target_id: 目标 ID（acunetix_list_targets 获取）

  • profile_id: 扫描配置 ID（acunetix_list_scan_profiles 获取）

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 15 tools

Disambiguation3/5

Most tools are clearly distinct (list_targets vs add_target vs start_scan), but acunetix_rest and acunetix_gql are generic executors that overlap with the specific list/get tools. The descriptions clarify their generic purpose, but an agent may still be uncertain whether to use the specific or generic tool for a given operation.

Naming Consistency3/5

All tools share the acunetix_ prefix, but naming patterns vary: some are verb-only (login, logout), some are nouns (me, gql, rest, stats), and some are verb_noun (list_targets, add_target). This mixed convention is still readable but not fully consistent.

Tool Count4/5

15 tools is within the typically well-scoped range, but the set feels slightly heavier because generic executors (acunetix_rest, acunetix_gql) are included alongside specific wrappers for the same endpoints. Each tool has some justification, though some redundancy exists.

Completeness4/5

Core workflows are covered: add target, start scan, list vulnerabilities, and list reports. However, there are no dedicated update/delete tools for targets or scans. The generic REST and GraphQL executors fill these gaps, so agents can work around them, but the dedicated tool surface is not fully complete.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources