constellation-mcp
Related Servers
Alternatives to constellation-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP-compatible agents to query security checklists, protocols, and framework mappings to safely build and operate AI agents, with tools for checklist runs, protocol lookup, mapping lookup, and threat search.9CC BY-4.0
- AlicenseNot gradedqualityCmaintenanceEnables LLM-driven security assessments by exposing Kali tools like nmap, httpx, sqlmap, and ffuf as MCP tools, with explicit planning, parallel tool calls, tiered memory, MITRE ATT&CK mapping, and human approval gates for intrusive operations.2MIT
- AlicenseNot gradedqualityCmaintenanceExposes Validin's threat intelligence and DNS, WHOIS, OSINT, certificate, crawl, and threat data as 55+ MCP tools for AI agents.MIT
- AlicenseAqualityBmaintenanceExposes the Maester security test framework for Microsoft 365/Entra/Defender as MCP tools, enabling AI agents to run tests, audit AI agents and MCP servers, and investigate security posture.9MIT
- FlicenseNot gradedqualityCmaintenanceExposes all PHANTOM security testing capabilities as MCP tools, enabling reconnaissance, vulnerability scanning, red teaming, and report generation through natural language interactions.2-
- AlicenseNot gradedqualityDmaintenanceIntegrates 7 security tools (nmap, nuclei, dirsearch, sqlmap, hydra, Acunetix, Metasploit) via MCP protocol for AI-assisted penetration testing with enterprise-grade safety features.1MIT
TDQS
Scored across 37 tools
All tools are cleanly separated by domain prefixes (mhangani_, gavaza_, nyarhi_) and each tool has a distinct purpose. Even similar operations like find vs search or report vs report are clearly differentiated by prefix and detailed descriptions, leaving no ambiguity.
Every tool name follows a consistent lowercase snake_case pattern with a domain prefix and a verb or verb+noun structure (e.g., mhangani_audit, gavaza_breach_add, nyarhi_add_node). No mixed conventions or inconsistent verb styles are present.
With 37 tools, the server is far beyond the typical well-scoped range of 3-15. While the tools are organized into three distinct domains, combining them makes the surface overly heavy and likely to overwhelm agents. Each domain would be better served as a separate server.
The audit and compliance domains have strong lifecycle coverage (authorize, audit, report, baseline, breach, requests, evidence). However, the knowledge graph domain lacks direct update and delete operations, relying only on undo, which is a notable gap for full graph management.