Skip to main content
Glama
rudraneel93

mcp-guardian

by rudraneel93

Related Servers

Alternatives to mcp-guardian

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A drop-in proxy that guards MCP servers with policy enforcement, secret redaction, prompt-injection screening, rug-pull detection, rate limiting, and audit logging.
      6 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Acts as an MCP gateway between AI agents and upstream tool servers, evaluating YAML policies on every tool call, injecting real credentials at the last mile, scanning requests and responses for secrets, PII, and prompt injection, and recording each action in a tamper-evident audit log. Also supports HTTP forward-proxy governance with rate limiting, cost tracking, and policy replay against historical audit data.
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Open-source MCP proxy that enforces security policies, content scanning, and audit logging between AI agents and tool servers
      25
      AGPL 3.0
    • A
      license
      A
      quality
      C
      maintenance
      Provides a security governance layer for AI agents to safely access upstream MCP servers, enforcing tool-level RBAC, parameter constraints, authentication via static tokens or OIDC, and tamper-evident audit logging.
      2
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for AI agent security guardrails. Provides input validation, prompt injection detection, PII redaction, output filtering, policy enforcement, rate limiting, and comprehensive audit logging.
      80 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Guardrail sidecar proxy between AI agents and their MCP/REST/CLI tools. Policy engine, human approval gates, time-limited grants, rate limiting, and OTEL tracing. One Go binary, one YAML config, fail-closed by default.
      1
      Apache 2.0

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct concern: costs, security, health, and the aggregate report. full_report is the only overlapping tool, but it is clearly positioned as a consolidated view rather than a duplicate.

    Naming Consistency4/5

    audit_costs, scan_security, and check_health follow a clear verb_noun pattern, but full_report breaks it by being a noun phrase instead of a verb-led action like generate_report. The pattern is still predictable and readable overall.

    Tool Count5/5

    At four tools, the server is compact and well-scoped for MCP health, security, and cost oversight. Each tool earns its place by covering a distinct diagnostic dimension, with no redundant or extraneous operations.

    Completeness5/5

    The set covers security scanning, cost auditing, health checks, and a combined reporting path, giving agents the full diagnostic workflow for MCP server oversight. No obvious dead ends or required operations are absent.

    Maintenance

    ActivityInactive
    ResponsivenessResponsive