Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/New1Direction/korgWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/new1direction/korg/introspect-mcp-ts-korg-recall-mcp)<a href="https://agentmods.dev/mcp/new1direction/korg/introspect-mcp-ts-korg-recall-mcp"><img src="https://agentmods.dev/badge/mcp/new1direction/korg/introspect-mcp-ts-korg-recall-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/new1direction/korg/introspect-mcp-ts-korg-recall-mcp"><img src="https://agentmods.dev/badge/mcp/new1direction/korg/introspect-mcp-ts-korg-recall-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
korg-recall-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"korg-recall-mcp": {
"command": "npx",
"args": [
"-y",
"@korgg/recall-mcp"
],
"env": {}
}
}What else server.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 10 lines scan A d60f21671e90
korg-recall-mcp is an MCP server published in the GitHub repository New1Direction/korg (4 stars, last pushed 23d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
remem
Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite. Runs locally from the @remem-ai/remem npm package.
thread-keeper
Multi-agent shared brain across Claude Code/Desktop, Codex, Antigravity CLI, Copilot, and VS Code. Cross-session memory, self-improving skill loops, inter-agent signaling — one local MCP server. Runs locally from the threadkeeper Python package.
usrcp
Encrypted local ledger of structured user state, shared across every MCP-aware AI tool. Runs locally from the usrcp npm package. Needs 1 environment variable to run.
reflect-mcp
Reflection's autonomous runtime — wake, read prior state, do useful work, write back, sleep. Runs locally from the reflect-mcp Python package.
engram
Persistent storage for local modules. Runs locally from the engram npm package.
june-mcp
MCP server for Junê — give any MCP agent (Claude Desktop, Claude Code, …) a shared, cited knowledge-graph memory backed by a June endpoint. Runs locally from the june-mcp Python package. Needs 13 environment variables to run.