Verdict — Compliance for AI-Generated Code MCP server
Compliance verdicts for AI-generated code. SOC 2, HIPAA, HITRUST for healthcare IT.
C57/100grade C
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed Verdict — Compliance for AI-Generated Code yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Verdict — Compliance for AI-Generated Code tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-09-27 · 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 qualitylocal package, no credentials required12/15
- Maintenancelast push 190 days ago4/15
- Maintainer identityregistry namespace matches repository owner7/10
Overall 57/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install Verdict — Compliance for AI-Generated Code in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
Verdict — Compliance for AI-Generated Code: common questions
- Is Verdict — Compliance for AI-Generated Code MCP server safe?
- With care: it is graded C, so read the findings first (57/100). Read the Verdict — Compliance for AI-Generated Code safety report
- Does Verdict — Compliance for AI-Generated Code need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Verdict — Compliance for AI-Generated Code maintained?
- The last commit was 206 days ago (2026-03-21). The latest release is v0.3.0.