Malicious Scanner MCP Server
Related Servers
Alternatives to Malicious Scanner MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to check URLs for scam/phishing risks, get verdicts with confidence and severity, report false positives, and monitor plan usage.33 npmMIT
- AlicenseCqualityDmaintenanceProvides 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.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables checking URLs against the PhishTank phishing database to identify malicious sites.4 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables scanning code and URLs for API deprecations, auditing websites for professional quality, and running resale value scans from photo URLs over MCP streamable HTTP.-
- AlicenseNot gradedqualityFmaintenanceA URL security scanner and MCP server that enables AI agents to analyze URLs for phishing, malware, and other threats before navigation, with optional intent alignment checks.6Apache 2.0
- AlicenseAqualityBmaintenanceEnables live website health checks including TLS, HTTPS, and security headers, returning an A-F grade with specific fixes.2MIT
TDQS
Scored across 1 tool
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.
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.
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.
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.