Opa Authz MCP server
Authorization answers from real policy code: evaluate Rego locally, or ask an AuthZEN 1.0 PDP.
B73/100grade B
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed Opa Authz yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Opa Authz tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 5 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 73/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
claude mcp add mcp-opa-authz -- docker run -i --rm ghcr.io/kanywst/mcp-opa-authz:0.3.0
Opa Authz: common questions
- Is Opa Authz MCP server safe?
- Mostly: it is graded B (73/100). Read the Opa Authz safety report
- How do I install Opa Authz?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Opa Authz need an API key?
- Yes. The registry entry asks for
AUTHZEN_PDP_TOKEN. - Is Opa Authz maintained?
- The last commit was 6 days ago (2026-09-14). The latest release is v0.3.0.