Developer · Local MCP server
Korg Ledger
Verifiable cognition: prove a session ledger is tamper-evident; audit & import any agent's logs.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.New1Direction/korg-ledger- Version
- 0.6.3
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-05-29
- Updated
- 2026-05-29
- Publisher
- New1Direction (GitHub) · 5 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/New1Direction) · how
- Repository
- github.com/New1Direction/korgex
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | korgex | 0.6.3 | stdio |
How to connect Korg Ledger
Korg Ledger runs locally from a Python package published to PyPI: korgex version 0.6.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx korgex. It reads these environment variables: KORG_JOURNAL_PATH and KORG_LEDGER_HMAC_KEY; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"korg-ledger": {
"command": "uvx",
"args": [
"korgex"
],
"env": {
"KORG_JOURNAL_PATH": "<value>",
"KORG_LEDGER_HMAC_KEY": "<value>"
}
}
}
}Derived from the registry entry, not tested here. 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 from New1Direction (GitHub)
| Server | Runs |
|---|---|
| dazai - burn-after-reading secret (motokano)Serve a secret to an agent exactly N times from locked RAM, then wipe it and self-destruct. | Local · stdio |
| Korg Introspect MCPWrap any korg:introspect@v1-aware binary as a Claude Code tool, honoring declared side-effects. | Local · stdio |
| Korg Recall MCPCross-vendor semantic memory: recall across Claude Code / Codex / Grok sessions by meaning. | Local · stdio |
| Trust OracleIndependent A-F trust grade for any MCP server, watched for drift. Free, never for sale. | Remote · HTTPLive check: ✓ handshake |
More developer servers
| Server | Runs |
|---|---|
| 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 |
| Korext: AI Code GovernanceGovernance copilot for AI-assisted coding. 72 packs, 532 rules, proof bundles. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Krabbot DevtoolsAI-agent-run devtools: package install risk, stack EOL/CVE checks, scored OSS bounties. | Remote · HTTPLive check: ✓ handshake |
| Krauncher analyzerHow long a GPU job will run and cost, before running it - static code analysis, never executed. | Local · stdio |
| KrimtoMemory for AI coding agents - markdown in your own git, not a vendor database. Apache-2.0. | Local · stdio |