Security Scanner
Scan URLs, IPs, domains and files for threats
Check URLs, domains, IPs, and file hashes against 70+ AV engines, URLhaus, AbuseIPDB, and ThreatFox. Probe targets for security headers and TLS. Scan for vulnerabilities. Generate risk-scored security reports.
Check if a URL is malicious, phishing, or suspicious by scanning it against 70+ security engines. Returns a verdict, detection count, and category classifications.
curl -H "Authorization: Bearer $TOOLROUTER_API_KEY" \
-d '{
"tool": "security-scanner",
"skill": "check_url",
"input": {
"url": "https://example.com"
}
}' \
https://api.toolrouter.com/v1/tools/callGet the threat reputation of a domain including detection stats from 70+ engines, DNS records, WHOIS data, registrar info, and popularity rankings.
curl -H "Authorization: Bearer $TOOLROUTER_API_KEY" \
-d '{
"tool": "security-scanner",
"skill": "check_domain",
"input": {
"domain": "example.com"
}
}' \
https://api.toolrouter.com/v1/tools/callLook up an IP address for threat intelligence including detection stats from 70+ engines, geolocation, ASN ownership, and network details.
curl -H "Authorization: Bearer $TOOLROUTER_API_KEY" \
-d '{
"tool": "security-scanner",
"skill": "check_ip",
"input": {
"ip": "8.8.8.8"
}
}' \
https://api.toolrouter.com/v1/tools/callLook up a file hash (MD5, SHA-1, or SHA-256) to check if the file is known malware. Returns detection stats from 70+ antivirus engines, sandbox verdicts, and file metadata.
curl -H "Authorization: Bearer $TOOLROUTER_API_KEY" \
-d '{
"tool": "security-scanner",
"skill": "check_hash",
"input": {
"hash": "275a021bbfb6489e54d471899f7db9d1663fc695ec2fe2a2c4538aabf651fd0f"
}
}' \
https://api.toolrouter.com/v1/tools/callScan web targets for security vulnerabilities by severity. Checks transport security, headers, and common exposure paths like .env and .git.
curl -H "Authorization: Bearer $TOOLROUTER_API_KEY" \
-d '{
"tool": "security-scanner",
"skill": "scan_targets",
"input": {
"targets": [
"example.com"
],
"severity": "medium"
}
}' \
https://api.toolrouter.com/v1/tools/callProbe multiple web targets for HTTP status, response times, TLS certificates, security headers, and technology signals. Scan up to 100 hosts concurrently.
curl -H "Authorization: Bearer $TOOLROUTER_API_KEY" \
-d '{
"tool": "security-scanner",
"skill": "probe_hosts",
"input": {
"targets": [
"example.com",
"https://openai.com"
]
}
}' \
https://api.toolrouter.com/v1/tools/callComprehensive one-shot security audit. Runs domain reputation, URL check, host probing, and vulnerability scan in parallel. Returns a unified risk score (0-100) with risk factors.
curl -H "Authorization: Bearer $TOOLROUTER_API_KEY" \
-d '{
"tool": "security-scanner",
"skill": "security_report",
"input": {
"target": "example.com"
}
}' \
https://api.toolrouter.com/v1/tools/callQuick Start
claude mcp add --transport stdio \
--env TOOLROUTER_API_KEY=YOUR_API_KEY \
toolrouter -- npx -y toolrouter-mcpcurl -H "Authorization: Bearer $TOOLROUTER_API_KEY" \
-d '{"tool":"security-scanner","skill":"check_url","input":{}}' \
https://api.toolrouter.com/v1/tools/callFrequently Asked Questions
What kind of checks does Security Scanner combine?
It combines reputation lookups for URLs, domains, IPs, and file hashes with host probing, vulnerability scanning, and a one-shot security report. That makes it useful when you want both threat intelligence and basic exposure checks in one place.
Which skill should I use for a suspicious site, server, or file?
Use `check_url` for a full URL, `check_domain` for a domain reputation check, `check_ip` for an IP address, and `check_hash` for a file hash. If you want a broader web-target assessment, use `probe_hosts`, `scan_targets`, or `security_report`.
Does it actively scan targets or only query threat feeds?
It does both. The reputation skills query security data sources, while `probe_hosts` inspects HTTP, TLS, and security headers and `scan_targets` checks for common exposures and vulnerabilities.
Is it instant or does it run asynchronously?
Most reputation checks return quickly. The broader `scan_targets` and `security_report` flows can take longer and are better treated as async security jobs.