Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Korext: AI Code Governance

REMOTE · APP.KOREXT.COM · 2 COMPONENTS · SCANNED SEP 22

Governance copilot for AI-assisted coding. 72 packs, 532 rules, proof bundles.

0 this week 81 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 350 tokens (~70/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Korext: AI Code Governance MCP server?

Korext: AI Code Governance is a hosted endpoint at https://app.korext.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · app.korext.com

# add to Claude Code
claude mcp add --transport http korext-governance 'https://app.korext.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "korext-governance": {
      "url": "https://app.korext.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "korext-governance": {
      "type": "http",
      "url": "https://app.korext.com/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.korext-governance]
url = "https://app.korext.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "korext-governance": {
      "type": "remote",
      "url": "https://app.korext.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add korext-governance --url 'https://app.korext.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  korext-governance:
    url: "https://app.korext.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "korext-governance": {
      "Transport": "http",
      "Url": "https://app.korext.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add korext-governance -t streamable-http -u 'https://app.korext.com/api/mcp'
// mcp.json
{
  "mcpServers": {
    "korext-governance": {
      "type": "http",
      "url": "https://app.korext.com/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Sept 2026 · Probed https://app.korext.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=app.korext.com CN=WR3,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 RSA 2048 SHA256-RSA 309c1dd65b8a66500a446b8b60ab432f
SANs: app.korext.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d
CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 1 Sept 1998 28 Jan 2028 RSA 2048 SHA1-RSA 40000000001154b5ac394

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.korext.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
korext.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self' https://*.googleapis.com https://*.firebaseapp.com; script-src 'self' 'unsafe-inline' https://apis.google.com https://*.gstatic.com https://*.firebaseapp.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: https:; font-src 'self' https: https://fonts.gstatic.com; connect-src 'self' https://app.korext.com https://*.googleapis.com https://*.firebaseio.com https://*.firebase.com https://*.firebaseapp.com https://storage.googleapis.com https://api.stripe.com https://identitytoolkit.googleapis.com https://securetoken.googleapis.com https://accounts.google.com https://github.com wss://app.korext.com; frame-src 'self' https://js.stripe.com https://accounts.google.com https://*.firebaseapp.com; object-src 'none'; frame-ancestors 'none'; upgrade-insecure-requests;
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.korext.com/api/mcp Verified 200
http (plaintext) http://app.korext.com/api/mcp HTTPS enforced 301 https://app.korext.com/api/mcp
MCP tools · 5 exposed · ~350 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_code ~69

Check a code snippet against one or more policy packs. Returns violations with severity, governance context (CWE, MITRE, regulatory), and line numbers.

NameTypeReqDescription
codestringyesThe code snippet to check.
packIdPolicy pack ID or array of IDs. Defaults to 'web'.

No output schema declared.

No examples provided.

generate_proof ~94

Scan code against policy packs and generate a cryptographically signed proof bundle. Returns the bundle ID, decision (PASS/BLOCK), violation count, and verification URL.

NameTypeReqDescription
codestringyesThe code to scan.
fileNamestringFile name for context
languagestringProgramming language (typescript, python, etc.)
packIdPolicy pack ID(s). Defaults to 'web'.

No output schema declared.

No examples provided.

get_directives ~77

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.

NameTypeReqDescription
packIdPolicy pack ID or array of IDs (e.g. 'web', ['web', 'pci-dss-v1']). Defaults to 'web'.

No output schema declared.

No examples provided.

get_proof ~45

Retrieve an existing proof bundle by ID. Returns the decision, violations, packs, and verification status.

NameTypeReqDescription
bundleIdstringyesThe proof bundle ID (kpb_...)

No output schema declared.

No examples provided.

list_packs ~65

List available policy packs with industry and region tags.

NameTypeReqDescription
industrystringFilter by industry (e.g. finance, healthcare, defense, aerospace, energy, technology)
regionstringFilter by region (e.g. us, eu, uk, global)

No output schema declared.

No examples provided.

Common questions

What is the Korext: AI Code Governance MCP server?

Korext: AI Code Governance is an MCP server listed in the public MCP registry as io.github.Korext/governance. Governance copilot for AI-assisted coding. 72 packs, 532 rules, proof bundles. This page covers its hosted endpoint (https://app.korext.com/api/mcp).

Is the Korext: AI Code Governance MCP server safe to use?

Korext: AI Code Governance scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Korext: AI Code Governance MCP server expose?

Korext: AI Code Governance exposes 5 tools: get_directives, check_code, list_packs, generate_proof, get_proof. Their descriptions and schemas cost roughly 350 tokens of context every time the server is loaded.

Does the Korext: AI Code Governance MCP server require authentication?

No. We connected to Korext: AI Code Governance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Korext: AI Code Governance MCP server still maintained?

Korext: AI Code Governance is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.