Eleion Scanner MCP

What the hernaninverso/eleion-scanner-mcp MCP server does

The hernaninverso/eleion-scanner-mcp MCP server exposes Eleion Scanner operations as tools for an AI agent. It connects to the hosted API at https://scanner-api.eleion.io and supports a workflow based on registered, verified domains.

An agent can register one of your domains, receive the DNS TXT or well-known record needed to prove ownership, and request verification after that record has been published. Once verification succeeds, the agent can queue a security scan and inspect its progress and results.

The scanner covers HTTP security headers, TLS, DNS, open ports, technology fingerprints, CVEs, and AI-specific checks. Findings include fields such as severity, CVE, template, title, and priority.

How it works

The workflow is sequential:

1. Call scanner_register_target(target_url) with a domain you control.
2. Publish the returned ownership record through DNS or the specified well-known location.
3. Call scanner_verify_target(target_id) to confirm ownership.
4. Start a scan with scanner_start_scan(target_id, scan_profile?).
5. Poll scanner_get_scan_status(scan_id) until the scan is completed.
6. Retrieve results with scanner_get_findings(scan_id).

The optional scan profile can be basic, full, or deep. Analysis runs on the Eleion side, so scans may not finish immediately, particularly for larger scan requests.

Setup and configuration

The hernaninverso/eleion-scanner-mcp MCP server runs through npx:

{
  "mcpServers": {
    "eleion-scanner": {
      "command": "npx",
      "args": ["-y", "eleion-scanner-mcp"],
      "env": {
        "SCANNER_API_KEY": "your_tenant_key"
      }
    }
  }
}

Set SCANNER_API_KEY to a tenant key obtained from https://scan.eleion.io. The configuration uses the standard MCP process-based setup and does not require a locally hosted scanning worker. The server submits work to the hosted Eleion Scanner API.

Tools and capabilities

• scanner_register_target(target_url): registers a domain and returns the record needed for ownership proof.
• scanner_verify_target(target_id): checks whether the ownership record has been published correctly.
• scanner_start_scan(target_id, scan_profile?): queues a basic, full, or deep scan for a verified target.
• scanner_get_scan_status(scan_id): reports scan progress and the current finding count.
• scanner_get_findings(scan_id): returns findings with severity, CVE, template, title, and priority data.

Limitations and notes

This is not an arbitrary-target scanner. Domains must be registered through the service and have their ownership verified before scanning. The scan worker operates server-side, so the agent should poll the status tool rather than assume that a queued scan has completed.

Registered domains and findings are processed by the hosted API. The project is MIT licensed. The hernaninverso/eleion-scanner-mcp MCP server is therefore best suited to authorized domain assessment workflows where the required tenant key and ownership records are available.