Skip to main content
Glama
BACH-AI-Tools

Malicious Scanner MCP Server

by BACH-AI-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Malicious Scanner MCP Server

No user-submitted related servers found.

    Related Servers

    • pleamo by pleamo

      pleamoofficial

      pleamo
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to check URLs for scam/phishing risks, get verdicts with confidence and severity, report false positives, and monitor plan usage.
      3
      10 npm
      MIT

    • Malicious URLs MCP Server

      BACH-AI-Tools
      A
      license
      C
      quality
      D
      maintenance
      Provides access to a malicious URL database API, enabling users to search, list, and retrieve information about potentially dangerous URLs for security analysis and threat detection.
      3
      MIT

    • mcp-phishtank

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables checking URLs against the PhishTank phishing database to identify malicious sites.
      21 npm
      MIT

    • linkcheck

      kazani-351
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to inspect a URL before opening, following, or recommending it, by tracing redirect chains via headers, stripping tracking parameters, detecting phishing-style URL tricks, and cross-checking threat-intel feeds to return a SAFE, SUSPICIOUS, or DANGEROUS verdict with supporting evidence. It also scans text for embedded and defanged links and vets agent skills prior to installation.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'scan_url' has a clearly defined and distinct purpose, making it impossible for an agent to misselect between multiple options.

    Naming Consistency5/5

    Since there is only one tool, naming consistency is inherently perfect. The tool name 'scan_url' follows a clear verb_noun pattern, and there are no other tools to compare it against, so no inconsistencies can arise.

    Tool Count2/5

    A single tool is generally too few for most server purposes, as it limits functionality and may indicate an incomplete or overly narrow scope. For a malicious scanner, one tool might suffice for basic scanning, but it lacks coverage for related operations like batch scanning, result management, or configuration adjustments.

    Completeness2/5

    The tool surface is severely incomplete for a malicious scanner domain. While 'scan_url' covers the core scanning function, there are obvious gaps such as scanning multiple URLs, retrieving scan history, managing whitelists/blacklists, or configuring scan parameters, which could lead to agent failures in more complex tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources