@mhdd_24/ai-red-team-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| airedteam_statusB | Show Structured robustness/security testing configuration / health. |
| airedteam_scanC | Scan text for policy/safety issues. |
| airedteam_suiteC | Generate a test suite outline. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clear, distinct purpose: status shows health/configuration, scan performs direct text analysis, and suite generates a test plan. There is no realistic confusion between them.
All tools share the consistent airedteam_ prefix and use lowercase snake_case, making the naming predictable. However, they do not follow a strict verb_noun pattern: scan is a verb while status and suite are nouns.
Three tools is at the lower end of the well-scoped range, but each one earns its place in a focused red-team utility server. There is no redundancy or unnecessary bloat.
The set covers health/status, text scanning, and test-suite outline generation, but there is no tool to execute a generated suite or retrieve detailed scan results. This leaves notable gaps in a full red-team testing workflow.