urlscan-mcp
Related Servers
Alternatives to urlscan-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for urlscan.io that scans URLs, searches historical scan data, and assesses indicators with compact, context-efficient summaries instead of raw API responses.14MIT
- AlicenseAqualityCmaintenanceAn MCP server wrapping urlscan.io and VirusTotal APIs to enable AI agents to pivot on threat indicators during investigations, with compact structured output and defanged results.6MIT

scanmalware-mcpofficial
AlicenseNot gradedqualityBmaintenanceWraps the ScanMalware.com API to enable phishing triage, malware scanning, and certificate inspection through natural language, allowing users to submit scans, retrieve results, and analyze threats via MCP tools.Apache 2.0- AlicenseNot gradedqualityBmaintenanceEnables searching past scans and submitting URLs for scanning via urlscan.io, with both keyless and key-based operations.170 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server that checks URLs against the URLhaus malware database to identify malicious URLs.-
- AlicenseNot gradedqualityBmaintenanceMCP server exposing tweetfeed.live's IOC feed (URLs, domains, IPs, hashes) as tools for querying threat intelligence, with checks, enrichment, trends, and campaign clustering.MIT
TDQS
Scored across 6 tools
Each tool has a distinct role: submission, result retrieval, free-form search, indicator-based pivoting, screenshot capture, and DOM inspection. No two tools overlap in purpose; even search_scans and pivot are clearly separated by query style and automation level.
Most tools follow a verb_noun pattern (scan_url, get_scan_result, get_screenshot, get_dom, search_scans), but 'pivot' is a single verb that stands out. Still, the names are intuitive and predictable, and the deviation is minor.
With 6 tools, the server is well-scoped for its purpose. Each tool addresses a core aspect of URL scanning and analysis, and there is no redundancy or bloat.
The tool set covers the full workflow: submit a URL, retrieve the summarized result, search historical scans, pivot on indicators, and inspect visual and textual evidence. No critical operations are missing for the intended use case of analyzing potentially malicious URLs.