Malicious URLs MCP Server
Related Servers
Alternatives to Malicious URLs MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables searching past scans and submitting URLs for scanning via urlscan.io, with both keyless and key-based operations.27 npmMIT
- AlicenseAqualityBmaintenanceEnables MCP clients to check URLs for scam/phishing risks, get verdicts with confidence and severity, report false positives, and monitor plan usage.310 npmMIT
- AlicenseBqualityDmaintenanceEnables real-time scanning of URLs for malicious content, spam/gray classification, and additional security flags like domain age through the Malicious Scanner API.1MIT
- AlicenseAqualityCmaintenanceMCP server for accessing URLhaus malicious URL database from abuse.ch - provides threat intelligence for cybersecurity research72 npm5MIT
- AlicenseNot gradedqualityBmaintenanceWraps abuse.ch URLhaus malware URL database (free, no auth) – enables querying malware URLs via natural language through Pipeworx MCP gateway.27 npmMIT
- AlicenseAqualityCmaintenanceMCP server that exposes urlscan.io as tools for security investigations, with compact results optimized for context windows. Enables pivoting on indicators, searching scans, retrieving screenshots, DOM, and scan results, and submitting URLs.6MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_random retrieves a single random URL, list_urls fetches a paginated list of all URLs, and search allows querying by URL. There is no overlap in functionality, making it easy for an agent to select the right tool.
The tool names follow a consistent verb-based pattern (get_random, list_urls, search), with all using snake_case. However, 'search' deviates slightly by not including a noun, which is a minor inconsistency in an otherwise predictable naming scheme.
With only 3 tools, the server feels thin for handling malicious URLs, as it lacks operations like adding, updating, or deleting URLs, or more advanced analysis features. While the tools cover basic retrieval, the scope seems limited for a domain that might benefit from more comprehensive management.
The tool surface is significantly incomplete for a malicious URL server, as it only provides read operations (random, list, search) with no ability to create, update, delete, or analyze URLs. This leaves obvious gaps in CRUD coverage and limits agents to passive querying without active management capabilities.