Imperva Cloud WAF MCP Server
OfficialRelated Servers
Alternatives to Imperva Cloud WAF MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Check Point CloudGuard WAF configuration through natural language, including assets, profiles, practices, and policy.1Apache 2.0
- AlicenseBqualityDmaintenanceProvides seamless integration with Fastly's Next-Gen Web Application Firewall API, enabling AI assistants to manage web application security through natural language interactions.291MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Cloudflare infrastructure including DNS records, cache purging, SSL settings, Workers, and analytics through the Cloudflare API. Eliminates dashboard context-switching by allowing natural language control of domain management and infrastructure operations.-

crowdsec-local-mcpofficial
AlicenseBqualityCmaintenanceGenerates, validates, and deploys CrowdSec WAF rules and scenarios through natural language.2426MIT- AlicenseNot gradedqualityDmaintenanceEnables natural language interaction with Cloudflare services including Workers, observability, documentation, and Radar for managing configurations, analytics, and internet insights.1,735 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query alerts, hunt threats, triage vulnerabilities, assess compliance, and run verified active-response actions across Wazuh deployments through natural-language tool calls. Supports cloud or local/air-gapped LLM clients with RBAC, audit logging, and scoped read/write access.MIT
TDQS
Scored across 4 tools
Each tool targets a distinct resource (domains, policies, rules, sites) with clear descriptions, so there is no ambiguity about which tool to use for a given purpose.
Tool names are inconsistent: some use 'by_filters', others 'of_account', and one uses 'of_a_given_account'. The 'tool' suffix is unnecessary and varies in placement. Naming pattern is not uniform.
With 4 tools, the set covers the main entities (sites, domains, policies, rules) without being overly numerous or sparse for a read-only WAF information server.
Only read operations are provided; there are no create, update, or delete tools for any resource. Agents cannot manage the WAF configuration, only retrieve existing data.