Skip to main content
Glama

Related Servers

Alternatives to opa-mcp-server

  • A
    license
    Not graded
    quality
    C
    maintenance
    A Model Context Protocol (MCP) server that provides safe, read-only access to Kubernetes resources for debugging and inspection. Built with security in mind, it offers comprehensive cluster visibility without modification capabilities.
    45
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    An MCP server that enforces authorization by evaluating Rego policies or querying an OpenID AuthZEN-compliant PDP, providing accurate access decisions for AI agents. It includes tools for policy evaluation, AuthZEN evaluation, batch evaluation, and PDP discovery.
    1
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables developers to wrap existing MCP servers with a deterministic policy enforcement gate that intercepts tool discovery and tools/call requests over stdio, allowing only authorized calls to reach the downstream server. It supports dynamic tool exposure or hiding, allow/deny/approval-required decisions, configurable error disclosure modes, and Ed25519-signed retry credentials for approved workflows.
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enforces deterministic security policies as an inline firewall for MCP server tool calls, with AST-based validation, cryptographic audit logging, and CLI-based evaluation and verification.
    MIT
  • A
    license
    B
    quality
    D
    maintenance
    A specialized MCP server that provides expert-level OpenFGA authorization modeling guidance, enabling users to create and manage authorization models for ReBAC systems directly from VS Code.
    2
    9
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    An MCP server that exposes governance, trust-scoring, compliance, guardrail, cost, drift, and supply-chain scanning tools and resources to any MCP client over stdio, Streamable HTTP, or legacy HTTP+SSE. It lets agents route every tool call through a deterministic five-way decision (allow, redact, require approval, deny, or quarantine) with hash-chained evidence, human approval workflows, and in-agent trust gates for LangChain, LangGraph, and Google ADK.
    30
    37 PyPI
    2
    MIT

TDQS

A3.7/5.0

Scored across 52 tools

Disambiguation3/5

Most tools have distinct purposes, but several evaluation/explanation tools overlap (rego_eval, opa_query_decision, opa_exec, rego_explain_undefined, rego_explain_decision, rego_eval_with_explain), and opa_config/opa_status are near-duplicates. Descriptions help, but with 52 tools misselection is easy.

Naming Consistency4/5

All names use snake_case with readable namespace/verb-noun components; prefixes (opa_, rego_, conftest_, mcp_) group tools by subsystem. However, the opa_/rego_ split is not perfectly consistent (opa_exec and opa_bundle_build are CLI-oriented like rego_ tools), and a few names are quite long.

Tool Count1/5

52 tools far exceeds the typical 3-15 range; even for a broad OPA ecosystem toolkit this is an extreme count that will overwhelm agents and increase selection errors.

Completeness5/5

The surface covers evaluation, formatting, checking, linting, testing, coverage, profiling, benchmarking, migration, bundles, server policies/data, Conftest, schema inference, formal verification, and sharing. Very few obvious gaps remain for an OPA-focused MCP server.

Maintenance

ActivityActive
ResponsivenessNo issues