Skip to main content
Glama
kali-mcp-server

kali-mcp-server

by rangta10

nikto_scan

Scans a target URL with Nikto to identify web server vulnerabilities and misconfigurations, optionally using SSL/HTTPS for HTTPS targets.

Instructions

Run Nikto web vulnerability scanner against a target URL

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "nikto_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
sslNoUse SSL/HTTPS
urlYesTarget URL to scan (e.g., http://example.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full burden and discloses almost nothing: it does not say the scan is intrusive/noisy, may be slow or long-running, may trigger IDS/WAF, or requires permission to run against the target. Only the mutation-adjacent nature of an active scan is implied by 'vulnerability scanner'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero wasted words, and the target concept appears before the scanner name would be needed. Brevity here is appropriate, though the terseness is part of the reason key behaviors go unstated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an active, potentially disruptive scanner with no annotations and no output schema, the definition should say something about duration, output, or safety expectations. As written, an agent knows only what to pass in, not what the call costs or produces.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with both url and ssl documented inline, so the schema already handles parameter meaning. The description adds nothing further about the ssl flag (e.g., that it must match the URL scheme) or the tolerated URL format, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Run'), a specific engine ('Nikto web vulnerability scanner'), and the resource ('target URL'). It implicitly differentiates from siblings like nmap_scan or sqlmap_scan by naming the tool, but it does not explicitly state the web-server-fingerprinting focus that separates it from them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no named alternatives, and no preconditions such as needing authorization or a reachable live host. The agent must infer from the vendor name alone that this is a web-server scan rather than a port or injection scan.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.