Developer · Remote MCP server
Korext: AI Code Governance
Governance copilot for AI-assisted coding. 72 packs, 532 rules, proof bundles.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Korext/governance- Version
- 3.0.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-04-15
- Updated
- 2026-04-15
- Publisher
- Korext (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Korext) · how
- Repository
- github.com/Korext/enforce-action.git
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.korext.com/api/mcp | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- korext-mcp 3.0.0 · protocol 2025-06-18
- Tools discovered
- 5:
get_directives,check_code,list_packs,generate_proof,get_proof - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | korext | 1.0.0 | stdio |
How to connect Korext: AI Code Governance
Korext: AI Code Governance is a remote MCP server: there is nothing to install. Its endpoint is https://app.korext.com/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a Node.js package published to the npm registry: korext version 1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y korext@1.0.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"governance": {
"command": "npx",
"args": [
"-y",
"korext@1.0.0"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Koncept MCP ServerQuery a curated YAML semantic concept graph for codebase invariants and cross-cutting facts. | Local · stdio |
| Kongen Labs - Pattern IntelligenceLLM reasoning regime detection, cross-domain pattern transfer, and model routing. | Local · stdio |
| KonQuest Meta Ads MCPSupervised Meta Ads operating system for Claude Code with 57 campaign management tools. | Local · stdio |
| KoragraphLocal multi-repo code graph over MCP. Blast radius, call graphs, and memory anchored to code. | Local · stdio |
| Korg Introspect MCPWrap any korg:introspect@v1-aware binary as a Claude Code tool, honoring declared side-effects. | Local · stdio |
| Korg LedgerVerifiable cognition: prove a session ledger is tamper-evident; audit & import any agent's logs. | Local · stdio |
| Korg Recall MCPCross-vendor semantic memory: recall across Claude Code / Codex / Grok sessions by meaning. | Local · stdio |
| Krabbot DevtoolsAI-agent-run devtools: package install risk, stack EOL/CVE checks, scored OSS bounties. | Remote · HTTPLive check: ✓ handshake |