jsscan-mcp
Related Servers
Alternatives to jsscan-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceSecurity checks for code an AI agent is about to trust. vetcode_guard checks a command before it installs packages or adds an MCP server: made-up names, look-alikes, malware advisories, brand-new releases, and the archive read without running it. vetcode_scan reads a folder for malware, supply-chain attacks, attacks on agents, leaked secrets and risky config. Local, zero dependencies.42MIT
- AlicenseAqualityDmaintenanceEnables AI agents to run Shipcheck on local JavaScript/TypeScript repositories, scanning for launch risks like exposed env vars, unsigned webhooks, and missing security guardrails.163 npmMIT
- AlicenseAqualityBmaintenanceEnables AI coding assistants to debug and analyze JavaScript in web pages by managing scripts, breakpoints, network and WebSocket traffic, browser state, and local file inputs/outputs for continuous reverse-engineering workflows.241,064 npmApache 2.0
- AlicenseAqualityCmaintenanceEnables compatible AI coding agents to inspect authorized software artifacts, analyze JavaScript/TypeScript and native binaries, optionally perform Ghidra decompilation, and produce verifiable evidence-linked technical reports.11MIT
- AlicenseAqualityDmaintenanceAgent-native "safe to ship?" security gate for AI-generated code. Uses real parsers and inter-rocedural taint analysis (JS/TS, Python, Go) to flag the classes AI coding agents get wrong — secrets, SQL injection, SS, SSRF, path traversal, command injection, weak JWT/CORS — and ranks findings by confidence. Exposes a scan tool over MCP.18 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control a local Chromium browser via CDP for page snapshots, screenshots, human-like interactions, autonomous crawling, API/GraphQL reconnaissance, authenticated differential testing, and Burp-like intercept, repeater, and intruder workflows with scope enforcement and audit logging.MIT
TDQS
Scored across 10 tools
Each tool has a clearly distinct role: scope inspection vs. URL scope checking, crawl-only vs. full scan, and finding listing vs. detail vs. verification are well separated. The descriptions make boundaries explicit, so an agent can select the right tool without confusion.
All tool names follow a consistent snake_case verb_noun pattern, such as get_scope, crawl_target, list_findings, and refresh_vuln_db. There are no mixed conventions or vague names.
Ten tools is well-scoped for a JavaScript security scanning server, covering scope, crawling, scanning, findings, verification, audit, and vulnerability database refresh. Each tool earns its place without obvious redundancy.
The surface covers the core scan lifecycle from scope checking through crawling, scanning, findings review, verification, and audit logging. Minor gaps exist around explicit false-positive rejection or report export, but agents can work around these using existing tools.