make-audit-mcp
Related Servers
Alternatives to make-audit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceStatically analyzes exported n8n automation workflows for security issues and returns structured findings.MIT
- 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.43 npmMIT
- AlicenseNot gradedqualityCmaintenanceLints n8n workflow exports and returns machine-readable findings with per-rule fixes, helping agents and reviewers catch reliability gaps such as missing error workflows, retries that swallow errors, unauthenticated webhooks, and hardcoded secrets without sending data anywhere.MIT
- AlicenseAqualityAmaintenanceEnables agents and CI pipelines to audit MCP servers and agent tool-chains by statically scanning repositories, local checkouts, tools/list exports, or live endpoints for risks such as destructive actions without confirmation, mismatched safety annotations, injection surfaces, credential or PII exposure, and unguarded command, path, or URL sinks. All checks are read-only and never execute the scanned code or call tools/call.3MIT
- FlicenseNot gradedqualityDmaintenanceAudits GitHub Actions workflow files for supply-chain risks like script injection, leaked tokens, unpinned actions, and broad permissions.-
- AlicenseBqualityCmaintenanceSafe MCP server and CLI tool for testing, scoring, and inspecting n8n workflows. Features 19 tools for workflow testing, execution traces, tiered scoring, and a built-in node catalog with 800+ node types. Designed with safety-first approach: no credential management, no secrets lifecycle, no auto-fix loops.191MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: inspect_blueprint provides a high-level overview, trace_module dives into a specific module, and audit_blueprint identifies risks. There is no overlap that would confuse an agent.
All tool names follow the verb_noun snake_case pattern (inspect_blueprint, trace_module, audit_blueprint), making the naming perfectly consistent and predictable.
With only 3 tools, the set is well-scoped for an audit-focused server. Each tool covers a necessary step in the workflow (overview, detail, risk assessment), and no tool feels extraneous.
The tools cover the full audit flow: inspect the blueprint for structure, trace modules for detail, and audit for risks. There are no obvious gaps, and the workflow is complete without dead ends.