Verdict — Compliance for AI-Generated Code

io.github.getverdict-aiPublished by GitHub account getverdict-aiv0.3.0Updated Oct 24, 2026

Compliance verdicts for AI-generated code. SOC 2, HIPAA, HITRUST for healthcare IT.

VerifiedSTDIODesktop onlyDeveloper Tools Security & Monitoring

Server details

Identifier: io.github.getverdict-ai/verdict
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account getverdict-ai for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.getverdict-ai%2Fverdict.svg)](https://sourceweft.com/mcp/io.github.getverdict-ai%2Fverdict?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that gives an assistant compliance verdicts on AI-generated code, aimed at SOC 2, HIPAA and HITRUST needs in healthcare IT.

What you can do: Produce compliance verdicts for AI-generated code
Assess code against SOC 2, HIPAA and HITRUST expectations for healthcare IT
No tool list is published, so the exact operations are not documented in the supplied material
When to use it: Worth considering when a team writes code with AI assistance in a regulated or healthcare context and wants compliance checks surfaced inside the assistant's workflow.
Requirements: Runs as a local process on the user's machine (desktop only, stdio transport). The README points to a Verdict CLI installed via a Homebrew tap; no environment variables, headers or authentication are declared.

Before you install

No tools, authentication or data-handling details are documented, so it is unclear what code is sent where or whether results are authoritative for an audit. Treat verdicts as guidance, not certification, and review the vendor's data policy before pointing it at proprietary source code.

Installation

In SourceWeft

Open Verdict — Compliance for AI-Generated Code in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Verdict CLI Releases

Binary releases for the Verdict CLI.

Source: README.md at commit e53400c

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.3.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts
Declare a license in the repository or the registry entry.