caldera-mcp
Related Servers
Alternatives to caldera-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceExposes the Mythic C2 framework as an MCP server so LLMs can operate agents, issue tasks, and query platform data conversationally.-
- AlicenseNot gradedqualityNot gradedmaintenanceConnects MCP clients to a Kali Linux terminal API, enabling AI-assisted penetration testing, CTF challenge solving, and automated security reconnaissance through command execution.1MIT
- AlicenseCqualityCmaintenanceEnables LLM agents to interact with and automate operations with the AdaptixC2 framework via the MCP protocol.5432GPL 3.0
- AlicenseBqualityDmaintenanceConnects any MCP-compatible AI client to Letta.ai's stateful agents for agent conversations, memory management, and tool orchestration.1812MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for orchestrating red team security assessments, enabling LLMs to manage agents, targets, operations, and findings aligned with MITRE ATT&CK framework.MIT
- FlicenseNot gradedqualityBmaintenanceProduction-grade MCP server that exposes Kali Linux penetration testing tools to AI agents, enabling automated reconnaissance, web application testing, vulnerability assessment, and more.-
TDQS
Scored across 18 tools
Every tool targets a distinct resource-action pair (ability, adversary, operation, agent). No two tools have overlapping purposes; even similar verbs like 'get' and 'list' are clearly differentiated by singular vs. plural. An agent can easily select the right tool.
All tools follow a consistent verb_noun pattern with the server prefix 'caldera_'. The verbs (create, delete, get, list, update, health_check, set) are uniform and predictable. No mixing of styles or ambiguous verbs.
18 tools is slightly above the typical 3-15 well-scoped range, but each tool serves a clear purpose for managing Caldera resources. The count feels justified given the domain (multiple CRUD operations, agent listing, health check, state management) and not excessive.
The tool surface covers CRUD for abilities, adversaries, and operations, plus agent querying and state management. Minor gaps exist: no update_ability or update_operation (though update_adversary is present), and no delete_agent. These are not critical but slightly reduce completeness.