ai-safety-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 |
|---|---|
| aisafety_statusC | Show Evaluate unsafe/problematic model outputs configuration / health. |
| aisafety_scanC | Scan text for policy/safety issues. |
| aisafety_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 addresses a clearly distinct activity: checking health/configuration, scanning text for issues, and generating a test suite outline. There is no meaningful overlap between these operations.
All tool names share the consistent 'aisafety_' prefix and are concise, but the naming style mixes nouns (status, suite) with an action-like word (scan). 'aisafety_suite' especially omits an explicit verb such as 'generate' or 'create'.
Three tools is a well-scoped count for a focused AI safety utility server. Each tool earns its place and covers a distinct core capability without unnecessary bloat.
The toolset covers core safety workflow needs: health check, scanning, and test suite generation. Minor gaps exist, such as the absence of a dedicated tool for detailed policy management or report retrieval, but the core surface is not incomplete.