BotArmor MCP server
Related Servers
Alternatives to BotArmor MCP server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables MCP clients to audit AI search visibility, generate intent-aligned social content, and assess Agentic Commerce Readiness with remediation files.3MIT
- AlicenseBqualityBmaintenanceEnables developers to audit MCP tool schemas and annotations, multi-agent delegation graphs, multi-turn behavioral drift, bias, and token/cost telemetry from inside their IDE or CLI, and to generate EU AI Act, NIST AI RMF, and SOC 2 compliance dossiers. It also provides sub-250ms inline circuit-breaking, adversarial IPIP-NEO-120 persona cohorts, stress testing, and chaos fault injection.121,255 npm1Apache 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- AlicenseAqualityBmaintenanceLets any MCP client, such as Claude, browse attack suites and probes, run a full assurance assessment with all reports written out, send custom prompts or multi-turn histories and get leak, PII and refusal checks back for adaptive attacks, and read findings from an earlier assessment. This enables agent-driven red-teaming of a chatbot, RAG app or AI agent without leaving the chat client.52MIT
- AlicenseAqualityDmaintenanceProvides prompt injection detection, PII/secrets redaction, and an audit trail for AI agents via MCP tools.4MIT
- AlicenseAqualityCmaintenanceProvides AI governance controls as MCP tools for safety screening, risk classification, and red teaming of AI systems, returning structured governance reports.32Apache 2.0
TDQS
Scored across 4 tools
Each tool maps to a clearly distinct part of the audit lifecycle: starting an audit, checking status, retrieving findings, and listing past audits. The status vs. report distinction is well explained by their descriptions.
All tools use consistent snake_case with a clear verb_noun pattern: start_audit, get_audit_status, get_audit_report, list_audits. The get_audit_* pair and list_audits are predictable and readable.
Four tools are well-scoped for an audit workflow and each earns its place. This is neither thin nor bloated for the stated purpose.
The core lifecycle is covered: start, poll status, retrieve report, and list audits. Minor gaps such as cancelling an in-progress audit or deleting old audits are not present but are unlikely to block normal use.