llm-assure-mcp
Related Servers
Alternatives to llm-assure-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to conduct penetration testing and offensive security workflows, including reconnaissance, exploitation, post-exploitation, threat intelligence, malware analysis, forensics, and reporting through MCP tools. It supports session management, C2, evasion, credential attacks, and many specialized security testing capabilities.1MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to perform authorized web security assessments through MCP tools and a guided review prompt, including passive and full scans, WAF detection, remediation fixes, report export, triage, scan comparison, and proof-of-control verification.1266 PyPI5MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI agents to run autonomous penetration testing and cybersecurity assessments with 150+ security tools, intelligent decision-making, and real-time reporting.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to orchestrate 100+ security tools over MCP for authorized penetration testing, including recon, scanning, exploitation, attack-chain planning, and knowledge-base retrieval.7Apache 2.0

Enkrypt AI MCP Serverofficial
AlicenseCqualityDmaintenanceIntegrates AI safety analysis, red-teaming, and prompt auditing directly into MCP-compatible clients like Claude Desktop and Cursor IDE, allowing real-time analysis of prompts and detection of jailbreak attempts.284Apache 2.0- AlicenseNot gradedqualityDmaintenanceAI red teaming toolkit exposed as a Model Context Protocol (MCP) server. Connect any MCP client and test AI systems for safety vulnerabilities.MIT
TDQS
Scored across 5 tools
The tools split cleanly by resource and action: suites and probes are listed separately, automated suite execution is distinct from single adaptive prompt sending, and findings retrieval is clearly separate from running an assessment. Descriptions reinforce the boundary between run_assessment and send_probe by emphasizing automated reporting versus multi-step manual probing.
All tool names follow a consistent snake_case verb_noun pattern: list_suites, run_assessment, list_probes, send_probe, get_findings. There are no mixed conventions or vague names.
Five tools is well-scoped for a red-team assessment server: discovery, execution, manual probing, and findings extraction are each represented without bloat. No tool feels redundant or missing from the core workflow.
The surface covers the assessment lifecycle: inspect suites, inspect probes, run automated assessments with reports, perform adaptive manual probes, and retrieve filtered findings. Target configuration is handled through file or inline arguments, so no obvious dead ends remain for the stated purpose.