wallcheck
Related Servers
Alternatives to wallcheck
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to scan a public URL in passive or authorized mode and receive only bounded, sanitized structured findings (severity, confidence, standard, evidence, remediation) with quarantined evidence instead of raw page dumps. A second tool lets agents inspect the scanner's safety boundaries and coverage without making any network request.MIT
- AlicenseBqualityCmaintenanceEnables read-only collection and comparison of Google Search Console and Bing Webmaster data, conservative URL protection, content auditing, reviewed-build verification, and private report generation through ten typed tools over stdio.10Apache 2.0
- AlicenseNot gradedqualityBmaintenanceExposes read-only local analysis tools for source auditing, web traffic review, binary reverse engineering, exploit scaffolding, OSINT, and reporting via JSON-RPC over stdio, enabling LLMs to orchestrate evidence-based security workflows without executing targets or sending network requests.1MIT
- AlicenseAqualityBmaintenanceProvides anonymous, privacy-preserving tools for AI agents, including prompt-injection scanning, site file validation, endpoint liveness checks, attestation, and risk-pattern analysis.34MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to investigate public URLs through evidence-first intelligence, including crawling, entity resolution, social discovery, SEO, technology detection, monitoring, reports, and optional AI reasoning.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform authorized web-pentest reconnaissance and interaction, including crawling, headless-browser control, login/BOLA comparisons, safe probes, HAR replay, and evidence-first reporting, while enforcing declared scope, audit trails, rate limits, and data minimization.1MIT
TDQS
Scored across 4 tools
probe_url and scan_exposure both perform a single honest GET and classify the wall, so their boundary is fuzzy; the scan_exposure description does clarify it adds secret-scanning, which helps, but an agent wanting wall classification alone has two plausible choices. audit is clearly domain-level and classify is clearly offline, so those two are distinct.
Two names are bare verbs (audit, classify) and two use verb_noun (probe_url, scan_exposure), so there is no single predictable pattern. All are snake_case and readable, but the convention is mixed.
Four tools is a sensible, tightly scoped surface for a read-only agent-access wall checker. The only redundancy is that scan_exposure subsumes probe_url, so one tool is arguably not earning a fully independent place.
The surface covers domain-level audit, single-URL probing, secret/exposure scanning, and offline classification of captured responses, which is good lifecycle coverage for a diagnostic tool. Minor gap: no batch or multi-URL operation despite the probes being read-only and cheap, forcing repeated single calls.