toolmoat
Related Servers
Alternatives to toolmoat
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA read-only MCP server that lets an agent audit its own environment by discovering local MCP configurations and skill folders on Windows, macOS, and Linux and running offline static checks for prompt injection, hidden instructions, hardcoded secrets, dangerous commands, unpinned packages, and excessive filesystem or transport permissions. It exposes tools to scan everything discovered, list configurations, vet a single skill, or analyze supplied text, returning text, JSON, SARIF, or HTML findings with CI-friendly severity levels.0MIT
- AlicenseAqualityAmaintenanceSecurity scanner for third-party AI agent-skill files: SKILL.md manifests, hooks, and bundled scripts, exposed via an MCP tool.117 npm2Apache 2.0
- AlicenseCqualityDmaintenanceSecurity scanner and MCP server that catches dangerous patterns in MCP servers and AI agent projects, such as leaked secrets, shell execution, and prompt-injection text. Runs as both a CLI and MCP server with CI-friendly severity gates.21MIT
- AlicenseAqualityDmaintenanceSecurity scanner for AI agent packages that enables AI agents to audit MCP servers and packages for vulnerabilities, prompt injection, and supply chain attacks.5163 npm3AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceSecurity scanner and runtime proxy for MCP servers. Catches tool poisoning, prompt injection, and rug-pull attacks (silent tool description changes) before they reach your AI agent. Includes a static scanner and a runtime stdio proxy.20 npmMIT
- AlicenseNot gradedqualityCmaintenanceSecurity scanner for MCP servers — vet an MCP before you wire it into an agent. Detects prompt-injection, credential exfiltration (via taint analysis), RCE, and supply-chain risks, and catches cross-server exfil chains no single server reveals. Zero-dependency local CLI, SARIF output, CI-gateable, no account.32 npmMIT
TDQS
Scored across 5 tools
The three scan tools are cleanly separated by input source: a filesystem path (scan_path), the already-installed agent environment (scan_installed), and inline content (scan_text). list_rules and list_pins cover reporting and proxy pin state respectively, so no two tools could plausibly be mistaken for each other.
Every tool follows a strict snake_case verb_noun pattern (scan_path, scan_installed, scan_text, list_rules, list_pins). The verbs are used consistently: scan_* for detection runs, list_* for read-only enumerations.
Five tools is well-scoped for a read-only security scanner: three input modes, one rule catalog, one pin-status view. Each tool earns its place and none appear redundant or bolted on.
The core lifecycle (scan a path, scan the installed environment, scan untrusted inline content) plus rule discovery and pin status is covered with no dead ends for a read-only tool. Minor gaps remain, such as retrieving a single rule by id or explaining a specific finding, but these are workable from list_rules output.