Scan any URL, domain, or IP address for security threats using URLScanner.online.
Returns a full security report including:
Threat verdict (safe / suspicious / malicious) and 0–100 security score
Threat intelligence across 70+ feeds (malware, phishing, blocklists)
SSL certificate validity, expiry, issuer, and OCSP status
HTTP security headers audit (missing / misconfigured)
DNS records (A, AAAA, MX, TXT, NS, SOA)
And More!
Free to use. No account required. 10 scans/day
Scored across 2 tools
The two tools have completely distinct purposes: scan_url initiates a new security scan, while get_scan retrieves results for an existing scan ID. There is no functional overlap or ambiguity in selection.
Both tools follow a consistent verb_noun pattern (scan_url, get_scan) using snake_case. The action verbs clearly indicate initiation vs. retrieval, establishing a predictable naming convention.
With only 2 tools, this falls into the 'borderline thin' category per the rubric. While it covers the absolute minimum submit-and-retrieve workflow, the lack of auxiliary operations (list scans, check rate limits) makes the surface feel sparse for managing the stated 10-scan daily quota.
The CRUD surface is minimal: only Create (scan) and Read (get result) are supported. Notable gaps include the inability to list recent scans (relevant given 1-hour retention), check remaining rate limit quota, or cancel in-progress scans—operations agents would need to avoid burning the strict 10-scan daily allowance.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
get_scanscan_url
