Skip to main content
Glama
README.md
# @mhdd_24/ai-guardrail-mcp

MCP server for Input/output policy validation.

Same architecture as [@mhdd_24/sublime-mcp](https://github.com/Mhdd-24/Sublime-MCP).

**Full documentation:** [docs/WIKI.md](./docs/WIKI.md)

---

## How it works (30 seconds)

```
You (chat) → MCP client → ai-guardrail-mcp → AI Guardrail APIs / CLIs / local tools
```

---

## Prerequisites

| Requirement | Notes |
|-------------|--------|
| **Node.js 18+** | ESM TypeScript MCP server |
| **Credentials / CLIs** | See environment variables below |

---

## Install

### Option A — npm (after publish)

```bash
npm install -g @mhdd_24/ai-guardrail-mcp
```

### Option B — npx

```bash
npx @mhdd_24/ai-guardrail-mcp
```

### Option C — clone and build

```bash
git clone https://github.com/Mhdd-24/AI-Guardrail-MCP.git
cd AI-Guardrail-MCP
npm install
npm run build
node dist/index.js
```

---

## Configure Cursor

Edit `~/.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "aiguard": {
      "command": "npx",
      "args": ["-y", "@mhdd_24/ai-guardrail-mcp"],
      "env": {
        "_": "optional"
      }
    }
  }
}
```

**Local development:**

```json
{
  "command": "node",
  "args": ["/absolute/path/to/AI-Guardrail-MCP/dist/index.js"]
}
```

---

## Environment variables

| Variable | Description |
|----------|-------------|
| — | No required env |

---

## Tools

| Tool | Description |
|------|-------------|
| `aiguard_status` | Show Input/output policy validation configuration / health. |
| `aiguard_scan` | Scan text for policy/safety issues. |
| `aiguard_suite` | Generate a test suite outline. |

---

## License

ISC

TDQS

B3.2/5.0

Scored across 3 tools

Disambiguation5/5

The three tools have clearly distinct purposes: status/health checking, text scanning, and test suite generation. There is no overlap or ambiguity between them, making tool selection straightforward.

Naming Consistency5/5

All tool names follow a uniform aiguard_ prefix pattern with a single lowercase descriptive word. This consistent naming convention makes the tool set predictable and easy to navigate.

Tool Count4/5

Three tools is a compact but reasonable size for a focused guardrail utility. Each tool has a distinct purpose, though the set could potentially be slightly expanded with additional related operations without feeling bloated.

Completeness3/5

The tools cover health/status, text scanning, and test outline generation, but notable gaps exist—there is no policy management or execution capability for the generated test suite. Specifically, aiguard_suite creates an outline with no way to run it, creating a dead end in the workflow.

Maintenance

ActivityMaintained
ResponsivenessNo issues