Eleion Scanner

io.github.hernaninversoPublished by GitHub account hernaninversov0.1.1Updated Oct 24, 2026

Register/verify your domains, queue security scans, and read findings (CVE, severity).

VerifiedSTDIODesktop onlyCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant register and verify your own domains, queue Eleion security scans, and read findings with severity and CVE details.

What you can do
Wraps the hosted Eleion Scanner API so an assistant can register a domain you own, retrieve the DNS TXT or well-known record needed to prove ownership, and verify it. It can then queue a scan (basic, full, or deep) over a verified target, poll the scan status and finding count, and list findings with severity, CVE, template, title, and priority. Scans cover headers, TLS, DNS, ports, technology fingerprinting, and AI-specific checks.
When to use it
Useful when you want an assistant to run recurring security checks on domains you control and summarize the results, for example reviewing exposed services, TLS configuration, or known CVEs. It is not intended for scanning arbitrary third-party targets, since only registered and verified domains can be scanned.
Requirements
Runs locally as an npm package via npx, so Node.js is needed. Requires a tenant API key supplied in the SCANNER_API_KEY environment variable, obtained from the Eleion service. Network access to the hosted Eleion Scanner API is required, and scans run server-side, so large scans take time and must be polled.
Before you install
The SCANNER_API_KEY is a secret tenant credential and should be kept out of shared configuration. Registering a target and starting a scan send your domain details to the hosted Eleion API, where registered domains and findings are processed. Ownership proof requires publishing a DNS TXT or well-known record for the domain. Scans are read-only against your own infrastructure but consume the service's scan capacity.

Installation

In SourceWeft

  1. Open Eleion Scanner in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Eleion Scanner — MCP server

Drive the Eleion security scanner from an AI agent: register one of your own domains, prove ownership, queue a security scan (headers, TLS, DNS, ports, tech-fingerprint, plus AI-specific checks), and read the findings — severity, CVE, title, priority. Wraps the hosted Eleion Scanner API (https://scanner-api.eleion.io).

Tools

ToolWhat it does
scanner_register_target(target_url)Register one of your domains; returns the DNS TXT / well-known record to publish for ownership proof.
scanner_verify_target(target_id)Verify the ownership record you published.
scanner_start_scan(target_id, scan_profile?)Queue a scan (basic/full/deep) over a verified target.
scanner_get_scan_status(scan_id)Poll a scan's status and finding count.
scanner_get_findings(scan_id)List the findings (severity, CVE, template, title, priority).

Setup

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

Get a tenant key at https://scan.eleion.io. You can only scan domains you have registered and verified ownership of — this is not an arbitrary-target scanner.

The scan worker runs the analysis server-side; large scans take time, so poll scanner_get_scan_status until completed. Your registered domains and findings are processed by the hosted API. MIT licensed.

Source: README.md at commit 0ea4abb

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.