Skip to content
Back to search

atomic-red-team-mcp

MCP server for Atomic Red Team

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/cyberbuff/atomic-red-team-mcp with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/cyberbuff/atomic-red-team-mcp'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/cyberbuff--atomic-red-team-mcp/badge.svg)](/listings/cyberbuff--atomic-red-team-mcp)

HTML

<a href="/listings/cyberbuff--atomic-red-team-mcp"><img src="/api/listings/cyberbuff--atomic-red-team-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

The Atomic Red Team MCP server can be installed in various development tools and AI assistants. Choose your platform below for detailed installation instructions:

Quick Start

**Recommended: Using uvx**

uvx atomic-red-team-mcp

**Using Docker**

docker run --rm -i ghcr.io/cyberbuff/atomic-red-team-mcp:latest

Platform-Specific Guides

- **[VSCode](https://github.com/cyberbuff/atomic-red-team-mcp/blob/main/docs/installation/code.md)** - Installation guide for VSCode - **[Claude Desktop & Claude Code](https://github.com/cyberbuff/atomic-red-team-mcp/blob/main/docs/installation/claude.md)** - Installation guide for Anthropic's Claude Desktop app and Claude Code CLI - **[Cursor](https://github.com/cyberbuff/atomic-red-team-mcp/blob/main/docs/installation/cursor.md)** - Installation guide for Cursor IDE - **[Windsurf](https://github.com/cyberbuff/atomic-red-team-mcp/blob/main/docs/installation/windsurf.md)** - Installation guide for Windsurf editor - **[Google AI Studio / Gemini](https://github.com/cyberbuff/atomic-red-team-mcp/blob/main/docs/installation/gemini.md)** - Installation guide for Google's AI tools - **[Other Tools](https://github.com/cyberbuff/atomic-red-team-mcp/blob/main/docs/installation/other.md)** - Cline, Zed, and generic MCP clients

Installation Methods

Each platform supports multiple installation methods:

1. **uvx (Recommended)** - Easiest setup, automatic updates 1. **Docker** - Isolated environment, consistent across systems 1. **Remote Server** ⚠️ - Hosted on Railway (free tier, may have limits)

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 145 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Atomic Red Team MCP Server
  2. An MCP (Model Context Protocol) server that provides access to Atomic Red Team tests.
  3. ## Available Tools and Resources
  4. The server provides the following MCP tools:
  5. - `query_atomics` - Search atomics by technique ID, name, description, or platform
  6. - `refresh_atomics` - Download latest atomics from GitHub
  7. - `validate_atomic` - Validate atomic test YAML
  8. - `get_validation_schema` - Get the atomic test schema
  9. - `execute_atomic` - Execute atomic tests (requires `ART_EXECUTION_ENABLED=true`)
  10. And resources:
  11. - `file://documents/{technique_id}` - Read atomic test files by technique ID
  12. ### Usage Examples
  13. - "Search mshta atomics for windows"
  14. - "Show me all the atomic tests for T1059.002"
  15. - "Find all the applescript atomics for macOS"
  16. - "Validate this atomic test YAML <yaml-content-here>"
  17. ## Installation
  18. The Atomic Red Team MCP server can be installed in various development tools and AI assistants. Choose your platform below for detailed installation instructions:
  19. ### Quick Start
  20. **Recommended: Using uvx**
  21. ```bash
  22. uvx atomic-red-team-mcp
  23. ```
  24. **Using Docker**
  25. ```bash
  26. docker run --rm -i ghcr.io/cyberbuff/atomic-red-team-mcp:latest
  27. ```
  28. ### Platform-Specific Guides
  29. - **[VSCode](https://github.com/cyberbuff/atomic-red-team-mcp/blob/main/docs/installation/code.md)** - Installation guide for VSCode
  30. - **[Claude Desktop & Claude Code](https://github.com/cyberbuff/atomic-red-team-mcp/blob/main/docs/installation/claude.md)** - Installation guide for Anthropic's Claude Desktop app and Claude Code CLI
  31. - **[Cursor](https://github.com/cyberbuff/atomic-red-team-mcp/blob/main/docs/installation/cursor.md)** - Installation guide for Cursor IDE
  32. - **[Windsurf](https://github.com/cyberbuff/atomic-red-team-mcp/blob/main/docs/installation/windsurf.md)** - Installation guide for Windsurf editor
  33. - **[Google AI Studio / Gemini](https://github.com/cyberbuff/atomic-red-team-mcp/blob/main/docs/installation/gemini.md)** - Installation guide for Google's AI tools
  34. - **[Other Tools](https://github.com/cyberbuff/atomic-red-team-mcp/blob/main/docs/installation/other.md)** - Cline, Zed, and generic MCP clients
  35. ### Installation Methods
  36. Each platform supports multiple installation methods:
  37. 1. **uvx (Recommended)** - Easiest setup, automatic updates
  38. 1. **Docker** - Isolated environment, consistent across systems
  39. 1. **Remote Server** ⚠️ - Hosted on Railway (free tier, may have limits)
  40. ## Configuration
  41. ### Environment Variables
  42. Check the `.env.example` file for a list of environment variables and their default values.
  43. #### Server Configuration
  44. - `ART_MCP_TRANSPORT` - Transport protocol (stdio, sse, streamable-http)
  45. - `ART_MCP_HOST` - Server host address (default: 0.0.0.0)
  46. - `ART_MCP_PORT` - Server port number (default: 8000)
  47. #### Repository Configuration
  48. - `ART_GITHUB_URL` - GitHub URL for atomics repository (default: <https://github.com>)
  49. - `ART_GITHUB_USER` - GitHub user/org (default: redcanaryco)
  50. - `ART_GITHUB_REPO` - Repository name (default: atomic-red-team)
  51. - `ART_DATA_DIR` - Local directory path where atomic test files are stored (default: ./atomics)
  52. #### Security Configuration
  53. - `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.**
  54. - Enable Authentication if you are hosting a remote MCP server
  55. #### Authentication Configuration
  56. - `ART_AUTH_TOKEN` - Static bearer token for authentication (optional, authentication disabled if not set)
  57. - `ART_AUTH_CLIENT_ID` - Client identifier for authenticated requests (default: authorized-client)
  58. ### Enabling Atomic Test Execution
  59. By default, the `execute_atomic` tool is **disabled** for safety reasons. To enable it:
  60. ```bash
  61. # Using uvx
  62. ART_EXECUTION_ENABLED=true uvx atomic-red-team-mcp
  63. ```
  64. **⚠️ 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.
  65. ### Authentication
  66. 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:
  67. ```
  68. Authorization: Bearer <your-token>
  69. ```
  70. **To enable authentication:**
  71. 1. Set the `ART_AUTH_TOKEN` environment variable:
  72. ```bash
  73. export ART_AUTH_TOKEN="your-secure-token-here"
  74. ```
  75. 1. Start the server (authentication is automatically enabled)
  76. 1. Clients authenticate by including the token in requests:
  77. ```bash
  78. curl -H "Authorization: Bearer your-secure-token-here" http://localhost:8000
  79. ```
  80. **Security Notes:**
  81. - Authentication is disabled by default (no token required)
  82. - When `ART_AUTH_TOKEN` is set, all requests must include a valid bearer token
  83. - Use strong, randomly generated tokens in production
  84. - Never commit tokens to version control
  85. - For development/testing, use a simple token. For production, use a cryptographically secure token
  86. **Example with Docker:**
  87. ```bash
  88. docker run --rm -i \
  89. -e ART_AUTH_TOKEN="my-secure-token" \
  90. -e ART_AUTH_CLIENT_ID="my-client" \
  91. ghcr.io/cyberbuff/atomic-red-team-mcp:latest
  92. ```
  93. ## Built With
  94. - [atomic-red-team](https://github.com/redcanaryco/atomic-red-team)
  95. - [atomic-operator](https://github.com/swimlane/atomic-operator)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.