io.github.kanywst/mcp-opa-authz

MCPcommunity
v0.3.1io.github.kanywstUnknownUpdated 7d agoGitHub

Authorization answers from real policy code: evaluate Rego locally, or ask an AuthZEN 1.0 PDP.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
7d agoLast update
Reads these credentials
  • AUTHZEN_PDP_TOKENAPI keyoptional

    Authorization header value for the PDP. A value with no scheme is sent as "Bearer <token>".

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.kanywst
LicenseUnknown
Version0.3.1
Sourcemcp-registry
GitHubkanywst/mcp-opa-authz
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 20, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source1mo ago

Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Authorization answers from real policy code: evaluate Rego locally, or ask an AuthZEN 1.0 PDP.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.