Skip to main content
Glama
Cyreslab-AI

urlhaus-mcp-server

by Cyreslab-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to urlhaus-mcp-server

No user-submitted related servers found.

    Related Servers

    • URLhaus Security Checker

      dmdund
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that checks URLs against the URLhaus malware database to identify malicious URLs.
      -

    • urlscan-mcp

      blackhole8080-darkmatter
      A
      license
      A
      quality
      B
      maintenance
      MCP server for urlscan.io that scans URLs, searches historical scan data, and assesses indicators with compact, context-efficient summaries instead of raw API responses.
      14
      MIT

    • mcp-urlhaus

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Wraps abuse.ch URLhaus malware URL database (free, no auth) – enables querying malware URLs via natural language through Pipeworx MCP gateway.
      2 npm
      MIT

    • virustotal-mcp-server

      barvhaim
      F
      license
      A
      quality
      D
      maintenance
      MCP server for security analysis using VirusTotal API, enabling AI assistants to analyze URLs, files, IP addresses, and domains with automatic relationship fetching.
      8
      1
      -

    • VirusTotal MCP Server

      w0h1v
      A
      license
      A
      quality
      B
      maintenance
      A MCP server for querying the VirusTotal API. This server provides tools for scanning URLs, analyzing file hashes, and retrieving IP address reports.
      11
      374 npm
      149
      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

    A3.9/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool targets a distinct resource or query mode: URL, host, payload, tag, and signature are clearly separated. The only mild ambiguity is between get_urls_by_tag and get_urls_by_signature, since both return filtered URL lists, but their descriptions clarify the filter type.

    Naming Consistency4/5

    Mostly follows a pattern where 'lookup_' means retrieve by a specific identifier/key and 'get_' means retrieve list-style data. However, get_urls_by_tag and get_urls_by_signature are also keyed queries but use 'get_' rather than 'lookup_', creating a minor inconsistency.

    Tool Count5/5

    Seven tools is well-scoped for a URLhaus threat intel server. Each tool maps to a distinct endpoint or query type, and none feels redundant or out of place.

    Completeness4/5

    The set covers the core read-only URLhaus workflows: recent URLs, recent payloads, URL/host/payload lookups, and URL filtering by tag or signature. A minor gap is the lack of payloads-by-tag or payloads-by-signature queries, but most main investigation paths are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources