Atomic Red Team Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Atomic Red Team Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
An MCP (Model Context Protocol) server that provides access to Atomic Red Team tests.
The server provides the following MCP tools:
query_atomics - Search atomics by technique ID, name, description, or platformrefresh_atomics - Download latest atomics from GitHubvalidate_atomic - Validate atomic test YAMLget_validation_schema - Get the atomic test schemaexecute_atomic - Execute atomic tests (requires ART_EXECUTION_ENABLED=true)And resources:
file://documents/{technique_id} - Read atomic test files by technique IDThe Atomic Red Team MCP server can be installed in various development tools and AI assistants. Choose your platform below for detailed installation instructions:
Recommended: Using uvx
uvx atomic-red-team-mcpUsing Docker
docker run --rm -i ghcr.io/cyberbuff/atomic-red-team-mcp:latestEach platform supports multiple installation methods:
Check the .env.example file for a list of environment variables and their default values.
#### Server Configuration
ART_MCP_TRANSPORT - Transport protocol (stdio, sse, streamable-http)ART_MCP_HOST - Server host address (default: 0.0.0.0)ART_MCP_PORT - Server port number (default: 8000)#### Repository Configuration
ART_GITHUB_URL - GitHub URL for atomics repository (default: <https://github.com>)ART_GITHUB_USER - GitHub user/org (default: redcanaryco)ART_GITHUB_REPO - Repository name (default: atomic-red-team)ART_DATA_DIR - Local directory path where atomic test files are stored (default: ./atomics)#### Security Configuration
ART_EXECUTION_ENABLED - Enable the execute_atomic tool (default: false). Set to true, 1, or yes to enable. ⚠️ WARNING: Only enable in controlled environments as this allows executing potentially dangerous security tests.#### Authentication Configuration
ART_AUTH_TOKEN - Static bearer token for authentication (optional, authentication disabled if not set)ART_AUTH_CLIENT_ID - Client identifier for authenticated requests (default: authorized-client)By default, the execute_atomic tool is disabled for safety reasons. To enable it:
# Using uvx
ART_EXECUTION_ENABLED=true uvx atomic-red-team-mcp⚠️ Security Warning: Only enable atomic test execution in controlled, isolated environments (like test VMs or sandboxes). These tests can modify system state, create files, execute commands, and perform actions that may be flagged as malicious by security tools.
The server supports static token authentication for securing access to the MCP tools and resources. When enabled, clients must include a bearer token in the Authorization header:
Authorization: Bearer <your-token>To enable authentication:
ART_AUTH_TOKEN environment variable: export ART_AUTH_TOKEN="your-secure-token-here" curl -H "Authorization: Bearer your-secure-token-here" http://localhost:8000Security Notes:
ART_AUTH_TOKEN is set, all requests must include a valid bearer tokenExample with Docker:
docker run --rm -i \
-e ART_AUTH_TOKEN="my-secure-token" \
-e ART_AUTH_CLIENT_ID="my-client" \
ghcr.io/cyberbuff/atomic-red-team-mcp:latest~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.