Skip to main content
Glama
NELPROINC

NEL VEIL MCP

by NELPROINC

Related Servers

Alternatives to NEL VEIL MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Domain security reconnaissance for AI agents — 13 tools (DNS+DNSSEC, SSL/TLS, HTTP security headers, SPF/DKIM/DMARC email auth, port scan, ASN, RDAP/WHOIS) plus a one-shot security_scan returning a 0–100 Health Score (A–F). Free, no API key.
      15
      70 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to register domains, prove ownership, queue security scans (headers, TLS, DNS, ports, tech-fingerprint), and retrieve findings with severity and CVE details via the Eleion Scanner API.
      5
      19 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with zero-cost, zero-dependency trust evaluation for domains, URLs, wallets, APIs, and IPs, returning a 0-100 score with SSL, DNS, WHOIS, security header, and content sub-scores, plus batch comparison to rank multiple targets.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to perform cybersecurity analysis including RDAP lookup, DNS analysis, SSL inspection, security header detection, and more, returning structured security reports.
      -
    • A
      license
      A
      quality
      A
      maintenance
      Security intelligence API for AI models. CVE lookup with EPSS/KEV, domain recon (DNS, WHOIS, SSL, subdomains, WAF), and code security checks (secrets, injection, headers). 16 tools, no API key required.
      55
      33
      MIT

    TDQS

    A4.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each check_* tool targets a distinct security aspect (email spoofing, TLS, headers, exposed files, subdomain takeover) with no overlap. scan_domain explicitly aggregates all passive checks and directs users to narrow tools for specific questions, while get_scan_report handles historical retrieval—all clearly differentiated.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern: check_* for individual checks, scan_domain for the full scan, and get_scan_report for retrieval. The naming is uniform and predictable, making tool selection obvious.

    Tool Count5/5

    With 7 tools, the server is well-scoped for a domain security scanner: five focused checks, one aggregate scan, and one report fetcher. Each tool earns its place without redundancy or bloat, fitting neatly within the ideal 3-15 range.

    Completeness5/5

    The tool surface covers the core lifecycle of domain security scanning: specific checks for common vulnerabilities, a full scan combining all modules, and retrieval of past scans. No obvious dead ends or missing operations exist within the stated passive-scanning scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues