crumplelab
Related Servers
Alternatives to crumplelab
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceExposes thirty callable tools that let any MCP client audit server manifests, detect poisoned tool descriptions, config files and long-term memory, catch tool rug-pulls, check known vulnerabilities and package authenticity, and statically screen tool code for SSRF, path traversal and command injection risk. It also simulates whether a proposed agent action should auto-approve or be held for human review.MIT
- AlicenseAqualityBmaintenanceMCP security server for AI coding agents. 12 tools: pre-install guardian, vulnerability audit, supply-chain attack detection via static code analysis, and CycloneDX 1.6 SBOM generation. Zero runtime dependencies.15120 npm15Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAudit any MCP server for tool-poisoning, prompt-injection, and data-exfiltration risk before connecting an agent.MIT
- FlicenseNot gradedqualityDmaintenanceA cryptographic sidecar proxy that tests MCP tools for OWASP vulnerabilities before deployment. Automatically sandbox and audit your AI agents' tool calls to ensure secure infrastructure.-
- AlicenseNot gradedqualityCmaintenanceEnables enterprise MCP security auditing through 12 deterministic no-LLM tools for evidence-gated claims, skill/prompt supply-chain audits, token profiling, and server auth-mode checks.MIT
- AlicenseBqualityDmaintenanceEnables deterministic security testing of AI agents that use tools by serving synthetic MCP environments with poisoned data, fake secrets, and privileged actions. Records agent tool calls and evaluates security invariants (e.g., canary leaks, forbidden access, approval binding) without an LLM judge or real systems.8MIT
TDQS
Scored across 3 tools
The three tools target clearly different surfaces: local AI-agent configuration, deployed web apps, and a reference list of attack traps. crumple_scan and crumple_site could be briefly confused as two audit modes, but the descriptions make the local-vs-deployed distinction explicit. crumple_traps is informational rather than an audit action, which is a mild mismatch in tool type but not genuinely ambiguous.
All tools share the consistent crumple_ prefix and snake_case formatting, making the set predictable and easy to recognize. However, the suffixes mix verb-like (scan) and noun-like (site, traps) forms, so it is not a uniform verb_noun convention.
Three tools is well-scoped for a focused security-audit server: one for local agent setups, one for deployed sites, and one reference tool for attack traps. Each tool has a clear reason to exist and none feels redundant or padded.
The surface covers the two main audit targets plus an explanatory trap catalogue, and crumple_site supports re-running after fixes. The main gap is that deeper database exposure checks cannot be performed by the server and must be delegated to the owner via CLI, though this is clearly documented as a workaround.