Eleion Scanner MCP Server

Eleion Scanner MCP server exists for a simple reason — assistants are far more useful when they can act on Eleion Scanner directly instead of describing what you should do. Register/verify your domains, queue security scans, and read findings (CVE, severity).

What you get

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

Configuration and credentials

You will need one environment variable: SCANNER_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by hernaninverso; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the eleion scanner mcp server does with a few real requests.