scanbase-mcp
OfficialRelated Servers
Alternatives to scanbase-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides agent-readiness audits of public websites via Cloudflare's scanner, enabling users to run scans, save reports, and enforce safety boundaries from natural language.MIT
- FlicenseNot gradedqualityCmaintenanceProvides AI agents with standardized security scanning capabilities for authorized assessments, including host detection, port scanning, service fingerprinting, web vulnerability scanning, CVE verification, and report generation, all with unified JSON output and strict compliance controls.-
- AlicenseAqualityAmaintenanceEnables AI coding agents to generate LGPD-compliant cookie banners by detecting trackers in local projects, and to scan published sites for privacy violations, returning actionable results.1857 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to analyze public websites, follow progress, retrieve shareable reports, compare multiple URLs, list checks and recent activity, and surface fixes ranked by impact.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables scanning any website for AI agent compatibility and marketing health, returning interactive dashboard reports with scores and revenue impact estimates.-
- AlicenseAqualityDmaintenanceProvides tools for AI agents to audit websites, including stack detection, DNS snapshots, and security checks.813 npmMIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: list_scans (history), get_scan (retrieve one scan by id), scan_site (perform a scan), list_checks (reference catalog), and account (quota/tier status). The potential overlap between list_scans and get_scan is well resolved by descriptions (list returns ids/summaries, get returns full saved findings).
Four of five tools follow a consistent verb_noun snake_case pattern (list_scans, list_checks, scan_site, get_scan). The lone outlier is 'account', a bare noun that breaks the verb_noun convention, but readability remains high.
Five tools is a tight, well-scoped set for a single-purpose compliance scanning service with no redundant tools. It is on the lean side, but every tool earns its place and none feels bloated.
Core lifecycle is covered: perform a scan, retrieve it, list history, see available checks, and check quota. Minor gaps exist (no delete/cleanup of stored scans, no explicit compare-scans or batch-scan operation), but agents can work around these via list_scans plus get_scan.