Skip to main content
Glama

@mhdd_24/ai-guardrail-mcp

MCP server for Input/output policy validation.

Same architecture as @mhdd_24/sublime-mcp.

Full documentation: docs/WIKI.md


How it works (30 seconds)

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

Related MCP server: sentinel-scan

Prerequisites

Requirement

Notes

Node.js 18+

ESM TypeScript MCP server

Credentials / CLIs

See environment variables below


Install

Option A — npm (after publish)

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

Option B — npx

npx @mhdd_24/ai-guardrail-mcp

Option C — clone and build

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:

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

Local development:

{
  "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

Available Tools

3 tools
aiguard_scanC

Scan text for policy/safety issues.

Inputs: text (required).

aiguard_statusA

Show Input/output policy validation configuration / health.

Inputs: no named parameters.

aiguard_suiteC

Generate a test suite outline.

Inputs: policy (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to scan tool manifests and server configs for prompt injection, tool poisoning, excessive agency, and other OWASP-mapped security issues directly through the scan_mcp_manifest tool.
      50 npm
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables users to deterministically audit MCP servers for security issues across manifests, source, runtime responses, multi-call state, identity, and install scripts, and to run an inline gateway that gates tool calls and scans responses before returning them.
      3
      25 PyPI
      1
      Apache 2.0