mcp-audit-168
Related Servers
Alternatives to mcp-audit-168
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLets an agent inspect and audit MCP servers before connecting to them, checking their exposed tools, prompts and resources for tool poisoning, shadowing, excessive permissions, leaked secrets and unsafe transports against 24 deterministic rules. Results are returned as findings with evidence, remediation and CWE/OWASP references, and can fail CI with SARIF, Markdown or standalone HTML reports.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAudits MCP server configurations and packages for security risks such as typosquats, credential exposure, and malicious code, with zero dependencies and no execution.1MIT
- AlicenseBqualityBmaintenanceScans MCP client configurations for risky settings without starting the configured servers. Returns redacted findings through a read-only MCP server and CLI226 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceAudit any MCP server for tool-poisoning, prompt-injection, and data-exfiltration risk before connecting an agent.MIT
- AlicenseNot gradedqualityBmaintenanceAudits MCP server configurations for security risks including capability inventory, SSRF, prompt injection, and drift detection. Works in read-only mode and can also be used as an MCP server to let AI agents audit their own attack surface.182 PyPI4MIT
- AlicenseAqualityBmaintenanceSecurity scanner for MCP servers: detects tool poisoning, hidden instructions, tool shadowing, excessive permissions, leaked secrets and weak transports before you install a server.4118 npmApache 2.0
TDQS
Scored across 5 tools
The three scan tools have some overlap because scan_to_sarif accepts local paths and public repos, overlapping scan_mcp_server and scan_public_repo. However, their outputs and targets are described clearly enough that an agent can distinguish them: SARIF export versus structured risk lists versus public-repo scanning.
All tool names use snake_case and begin with a verb: list_rules, explain_rule, scan_mcp_server, and scan_public_repo follow a clear verb_noun pattern. scan_to_sarif is a minor deviation because it names an output format rather than a target object, but it remains predictable.
Five tools are well scoped for a focused MCP security-audit server: rule discovery, rule explanation, local scanning, public-repo scanning, and SARIF export. Each tool has a clear role and the set does not feel padded.
The set covers the core workflow: inspect rules, explain a rule, scan local MCP servers, scan public repos, and export SARIF. Minor gaps remain, such as no rule filtering/configuration, no batch or history view, and no result comparison, but the main audit lifecycle is present.