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.14 npmMIT
- AlicenseAqualityBmaintenanceSecurity scanner for third-party AI agent-skill files: SKILL.md manifests, hooks, and bundled scripts, exposed via an MCP tool.186 npm3Apache 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.588 npm3AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceSecurity 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.57 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.60 npmMIT
TDQS
Scored across 5 tools
The three scan tools are cleanly separated by input source: installed setup, filesystem path, and inline text. The two list tools are also distinct: pinned MCP servers versus detection rules.
All tool names follow a consistent snake_case verb_noun pattern. The scan_* and list_* prefixes make the tool families predictable.
Five tools is well-scoped for a security scanner: three scan entry points plus two read-only listing tools. Each tool has a clear reason to exist.
The surface covers scanning installed setups, individual paths, and inline content, plus rule discovery and pin visibility. Minor gaps exist around detailed pending-change review or accepting changes, but the description indicates acceptance is intentionally user-only in a terminal.