zscaler-aiguard-control-plane-mcp
Related Servers
Alternatives to zscaler-aiguard-control-plane-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceProvides secure access to the LogicMonitor API, enabling AI assistants to manage monitoring infrastructure through natural language commands.16 npm6Mozilla Public 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage zrok tunnels, shares, and access programmatically through environment management, share creation/deletion/listing, and access control actions.MIT

Britive MCP Serverofficial
FlicenseNot gradedqualityDmaintenanceEnables AI agents and users to interact with the Britive platform for dynamic access, query configurations, reporting, and access activity.1-- AlicenseBqualityCmaintenanceEnables AI agents to directly manage Beyond Identity resources such as identities, groups, applications, SSO configurations, and credentials via natural language tool calls.363 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceConnects AI agents with the CrowdStrike Falcon platform to enable intelligent security analysis, providing programmatic access to detections, incidents, threat intelligence, vulnerabilities, and other security capabilities for advanced security operations and automation.256MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to investigate threats, pull reports, manage security policies, and administer deployment infrastructure through the Cisco Secure Access REST API.-
TDQS
Scored across 18 tools
Tools are clearly distinguished by resource type and action (e.g., list_llm_providers vs. get_llm_provider). The only potential ambiguity is between list_policies and list_policy_summaries, but descriptions clarify their differences.
All tool names follow the verb_noun pattern with snake_case, and prefixes like list_, get_, update_, delete_, create_, and check_ are used consistently across resources.
18 tools is reasonable for managing multiple resource types (LLM providers, applications, match rules, policies), though it is slightly high. The count is within the typical well-scoped range.
Missing create operations for LLM applications, providers, and match rules, and missing delete for applications and match rules. This creates workflow gaps where new resources cannot be created from scratch via the MCP.