Korext: AI Code Governance
Server Details
Governance copilot for AI-assisted coding. 72 packs, 532 rules, proof bundles.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- Korext/enforce-action
- GitHub Stars
- 4
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 5 tools
Most tools have clear, distinct purposes: check_code returns violations, generate_proof creates a signed bundle, get_directives retrieves rules, get_proof fetches a bundle, and list_packs enumerates packs. The only potential ambiguity is between check_code and generate_proof, both scan code against policies, but they produce different outputs (raw violations vs. proof bundle), making them distinguishable.
All five tool names follow a consistent verb_noun pattern (check_code, generate_proof, get_directives, get_proof, list_packs). The verbs are action-oriented and the nouns clearly indicate the resource or output, with no mixed conventions or vague naming.
Five tools is well-scoped for a code governance server. Each tool addresses a distinct aspect: checking, proof generation, policy retrieval, proof retrieval, and pack listing. This covers the core workflows without unnecessary redundancy or bloat.
The tool surface covers the primary governance operations: checking code, generating and retrieving proofs, and accessing policy directives and pack listings. Minor gaps exist, such as no direct method to view a single policy pack's full details or manage packs, but the core enforcement and proof lifecycle is complete.
Available Tools
5 toolscheck_codeAInspect
Check a code snippet against one or more policy packs. Returns violations with severity, governance context (CWE, MITRE, regulatory), and line numbers.
Inputs: code (required), packId.
generate_proofAInspect
Scan code against policy packs and generate a cryptographically signed proof bundle. Returns the bundle ID, decision (PASS/BLOCK), violation count, and verification URL.
Inputs: code (required), packId, fileName, language.
get_directivesAInspect
Get enriched policy directives and living standards for one or more policy packs. Returns rules with governance context (CWE, MITRE, regulatory references) for inference time enforcement.
Inputs: packId.
get_proofAInspect
Retrieve an existing proof bundle by ID. Returns the decision, violations, packs, and verification status.
Inputs: bundleId (required).
list_packsAInspect
List available policy packs with industry and region tags.
Inputs: region, industry.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
AI code governance and code review for Claude Code, Copilot and Cursor. Checks rules and security.
Runtime AI governance: decision gates, human approval, hash-chained audit, compliance mapping.
Governed behavior for AI applications and coding agents: define, evaluate, release and inspect.
Governance maturity assessment, compliance gap analysis, and evidence-linked briefs for AI agents.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceDeterministic AI code review with audit records, providing stack-specific rulesets and governance for coding agents.5MIT

Rigour MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to self-govern by scanning code for hardcoded secrets, structural violations, and AI drift in real-time, providing fix packets for automatic remediation.29MIT- AlicenseBqualityBmaintenanceCommit-time audit engine for AI coding agents. Scans git diffs with 24 audit rules, writes HMAC-signed tamper-evident audit history, and ships MCP tools for governance aggregation.10456MIT

corbatofficial
AlicenseAqualityDmaintenancePolicy and quality engine for AI coding agents that enforces team coding standards and provides validation gates for agent-assisted software delivery.754 npm5MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.