Eleion Scanner MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCANNER_API_KEY | Yes | Your tenant key for the Eleion Scanner API |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scanner_register_targetA | Register one of YOUR OWN domains/URLs to be security-scanned. Returns a verification_token plus the DNS TXT record (or /.well-known URL) you must publish to prove ownership before scanning. You can only scan domains you own. |
| scanner_verify_targetA | Verify domain ownership of a previously registered target by checking the DNS TXT / .well-known record you published. Returns whether verification succeeded. |
| scanner_start_scanA | Queue a security scan over a target you have already registered AND verified. Returns a scan_id and status. Poll scanner_get_scan_status until completed, then read scanner_get_findings. |
| scanner_get_scan_statusA | Get the status of a scan (queued|running|completed|failed) and how many findings it has. |
| scanner_get_findingsA | List the security findings of a completed scan (severity, CVE, template, title, URL, priority_score), ordered by priority. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct step in the scanning workflow: registration, verification, scan start, status polling, and findings retrieval. No two tools overlap in purpose, making selection unambiguous.
All tools follow a consistent 'scanner_verb_noun' pattern with snake_case (e.g., scanner_get_findings, scanner_register_target). The prefix and structure are uniform across all five tools.
With 5 tools, the server is well-scoped for its purpose—managing security scans. Each tool addresses a necessary step, and the count is neither too thin nor overly heavy for the domain.
The tool set covers the full scan lifecycle: register, verify, start, poll status, and retrieve findings. Minor gaps like a tool to delete or list targets exist but do not hinder the primary workflow.