Skip to main content
Glama
Sign In
opa-mcp-server

opa-mcp-server

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to opa-mcp-server

  • kubernetes-mcp

    kkb0318
    A
    license
    Not graded
    quality
    D
    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

  • mcp-opa-authz

    kanywst
    A
    license
    Not graded
    quality
    B
    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

  • Dmint MCP Proxy

    dmint-app
    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

  • SentinelMCP

    ateeqdesktop-dot
    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

  • astrix

    vivek5200
    A
    license
    A
    quality
    B
    maintenance
    Agentic DevOps control loop and MCP server featuring polyglot Tree-sitter AST blast-radius analysis, OPA Rego policy evaluation, and isolated --network=none Docker test verification[cite: 1]. Exposes tools to inspect impacted dependency closures, validate security guardrails, and run targeted test suites.
    3
    2
    Apache 2.0

  • WhitePact

    Guruprasath-Annadurai
    F
    license
    A
    quality
    C
    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
    -
Deploy Server
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

TDQS

A3.7/5.0

Scored across 52 tools

Disambiguation2/5

Several clusters have blurred boundaries: rego_eval, rego_eval_with_profile, rego_eval_with_explain, rego_eval_with_coverage, rego_explain_decision, rego_explain_undefined, opa_exec, and opa_query_decision all answer overlapping evaluation/debug questions. opa_status and opa_config explicitly return the same underlying document, and rego_test/rego_test_multiroot/conftest_verify plus rego_format/rego_format_write are easy to misselect. Descriptions are detailed, but with 52 tools the risk of choosing the wrong variant remains high.

Naming Consistency4/5

Names are consistently snake_case and use clear domain prefixes (rego_, opa_, conftest_), with bundle operations grouped under opa_bundle_. The pattern is not a uniform verb_noun scheme—some names are action+object and some use long variant suffixes—but it is predictable overall.

Tool Count2/5

At 52 tools, the set is far beyond a well-scoped 3-15 tool surface and creates substantial context and selection burden. Many specialized variants, such as the eval-with-* tools and status/config duplication, could be consolidated into fewer tools with flags.

Completeness5/5

The surface covers the Rego policy lifecycle unusually thoroughly: authoring, evaluation, tracing, testing, coverage, linting, formatting, schema inference/checking, migration, verification, bundles, policy/data CRUD, and Conftest workflows. There are essentially no dead ends for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues

Resources