Eleion Scanner
NPM · ELEION-SCANNER-MCP · SCANNED AUG 3
Register/verify your domains, queue security scans, and read findings (CVE, severity).
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 33 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 289 tokens (~57/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · eleion-scanner-mcp
claude mcp add hernaninverso-eleion-scanner-mcp -- npx -y eleion-scanner-mcp
codex mcp add hernaninverso-eleion-scanner-mcp -- npx -y eleion-scanner-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hernaninverso-eleion-scanner-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"eleion-scanner-mcp"
],
"enabled": true
}
}
} openclaw mcp add hernaninverso-eleion-scanner-mcp --command npx --arg -y --arg eleion-scanner-mcp
mcp_servers:
hernaninverso-eleion-scanner-mcp:
command: "npx"
args: ["-y", "eleion-scanner-mcp"] {
"mcpServers": {
"hernaninverso-eleion-scanner-mcp": {
"command": "npx",
"args": [
"-y",
"eleion-scanner-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +43
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
- 31 Jul 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
scanner_get_findings ~48
List the security findings of a completed scan (severity, CVE, template, title, URL, priority_score), ordered by priority.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_id | string | yes | The scan id. |
No output schema declared.
No examples provided.
scanner_get_scan_status ~43
Get the status of a scan (queued|running|completed|failed) and how many findings it has.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_id | string | yes | The scan id. |
No output schema declared.
No examples provided.
scanner_register_target ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| target_url | string | yes | The http(s) URL/domain to register (must be a public host you control). |
No output schema declared.
No examples provided.
scanner_start_scan ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_profile | string | — | Scan depth. |
| target_id | integer | yes | The verified target id. |
No output schema declared.
No examples provided.
scanner_verify_target ~51
Verify domain ownership of a previously registered target by checking the DNS TXT / .well-known record you published. Returns whether verification succeeded.
| Name | Type | Req | Description |
|---|---|---|---|
| target_id | integer | yes | The target id returned by scanner_register_target. |
No output schema declared.
No examples provided.