MCP server providing access to Atomic Red Team security tests with search, validation, and creation capabilities
This MCP server has reasonable naming conventions and decent overall structure, but suffers from inconsistent parameter documentation, missing output schema details, and lack of error handling guidance. 5 of 7 tools have descriptions exceeding the 20-char minimum, but several parameters lack descriptions entirely (e.g., 'limit', 'cursor' in query_atomics). Tool schemas are visible in the input definitions but output schemas are not documented in the rubric data provided. The server shows effort in security awareness (DESTRUCTIVE risk annotation for execute_atomic) and composition (7 single-responsibility tools), but falls short of production-grade standards in parameter clarity and error recovery guidance.
Execute an atomic test by GUID (requires ART_EXECUTION_ENABLED=true)
Generate an atomic test using AI assistance
Get the JSON schema for atomic test structure
Search existing atomic tests by technique ID, name, description, or platform
Update atomic tests from GitHub repository
Get comprehensive information about the MCP server configuration and environment. This tool returns server metadata including version, transport protocol, operating system, and data directory location. Use this to: - Verify server configuration - Check server version for compatibility - Confirm the platform before executing atomic tests - Locate the atomic tests data directory
refresh_atomics lacks actionable description, does not explain when to call it, what it modifies, or whether it's idempotent
query_atomics 'limit' and 'cursor' parameters have descriptions but no type constraints (min/max for limit; format for cursor)
No error handling guidance in any tool description. Tools do not document retryable vs. fatal errors, or what the LLM should do on failure.
execute_atomic requires ART_EXECUTION_ENABLED environment variable, but tool description does not advise user/LLM what to do if execution is disabled
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 67 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 0 | - | v1 |
Validate atomic test YAML against the schema
Output schemas not documented in tool descriptions. Downstream tools and LLMs cannot determine what fields to expect from responses.
get_validation_schema has minimal description (12 words). LLM cannot determine when to call it vs. validate_atomic.