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.

com.kage-core/kage

NPM · @KAGE-CORE/KAGE-GRAPH-MCP · SCANNED SEP 24

Verified memory for coding agents: claims cited against code, stale withheld, savings receipts.

−1 this week 78 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 99 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 4519 tokens (~68/item across 66 items; 66 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 17% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "kage_context_slot_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 66 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 com.kage-core/kage MCP server?

com.kage-core/kage runs locally as an npm package, launched with npx -y @kage-core/kage-graph-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @kage-core/kage-graph-mcp

# add to Claude Code
claude mcp add com-kage-core-kage -- npx -y @kage-core/kage-graph-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "com-kage-core-kage": {
      "command": "npx",
      "args": [
        "-y",
        "@kage-core/kage-graph-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-kage-core-kage": {
      "command": "npx",
      "args": [
        "-y",
        "@kage-core/kage-graph-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-kage-core-kage -- npx -y @kage-core/kage-graph-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-kage-core-kage": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@kage-core/kage-graph-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-kage-core-kage --command npx --arg -y --arg @kage-core/kage-graph-mcp
# ~/.hermes/config.yaml
mcp_servers:
  com-kage-core-kage:
    command: "npx"
    args: ["-y", "@kage-core/kage-graph-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-kage-core-kage": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@kage-core/kage-graph-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-kage-core-kage -t stdio -c npx -a -y @kage-core/kage-graph-mcp
// mcp.json
{
  "mcpServers": {
    "com-kage-core-kage": {
      "command": "npx",
      "args": [
        "-y",
        "@kage-core/kage-graph-mcp"
      ]
    }
  }
}
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.

  • 23 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 22 Sept 26 +1
    • Stability: 0.97 → pass security
  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

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 24 Sept 2026 · Analysed npm/@kage-core/kage-graph-mcp@2.3.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 99 packages
Packages resolved 99
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 66 exposed · ~4,519 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
kage_audit ~48

Audit whether repo memory and code intelligence are trustworthy: validation, memory inbox, structured context coverage, code graph precision, graph links, and concrete recommendations.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_benchmark ~61

Return Kage proof metrics, or set mode=memory_quality / memory_scale for synthetic memory retrieval benchmarks.

NameTypeReqDescription
modestring––
project_dirstringyes–
sizesarray––
top_knumber––

No output schema declared.

No examples provided.

kage_benchmark_compare ~62

Compare the same task on the same repo with and without Kage. Reports estimated baseline discovery tokens/steps versus Kage recall/code-graph context, with evidence and caveats.

NameTypeReqDescription
project_dirstringyes–
taskstringyes–

No output schema declared.

No examples provided.

kage_branch_overlay ~40

Build and return branch overlay metadata: branch, head, merge-base, changed files, and pending packet IDs.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_capabilities ~44

Return an evidence-backed Kage memory-system capability audit across repo memory, collaboration/session proof, benchmarks, and dashboard/viewer readiness.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_capture ~138

Create a repo-local Kage memory packet immediately. Org/global promotion still requires explicit human review. Capture is rejected if every referenced path is missing from the repo; set allow_missing_paths to record anyway.

NameTypeReqDescription
allow_missing_pathsboolean––
bodystringyes–
graph_nodesarray–Code-graph node references (symbol/route/file) this memory is about.
pathsarray––
project_dirstringyes–
stackarray––
summarystring––
tagsarray––
titlestringyes–
typestring––

No output schema declared.

No examples provided.

kage_cleanup_candidates ~54

Find conservative cleanup candidates from Kage's code graph. Reports unreferenced source files, unused exports, and internal-looking unused symbols with confidence and reasons; never auto-deletes.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_code_graph ~72

Query the source-derived codebase graph: files, symbols, imports, calls, routes, tests, package scripts. This is generated from code, not learned memory.

NameTypeReqDescription
jsonboolean––
limitnumber––
project_dirstringyes–
querystring––

No output schema declared.

No examples provided.

kage_code_index ~56

Write external code index artifacts consumed by the code graph. Prefers SCIP when scip-typescript and scip are installed, then falls back to the built-in LSP-compatible symbol index.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_compact ~89

Consolidate repo memory: prune dead citations, deprecate hard-stale packets, and surface near-duplicate clusters to merge (via kage_supersede). Defaults to a dry run; pass dry_run=false to apply pruning/deprecation. Duplicate merging stays an agent decision — no hosted LLM is used.

NameTypeReqDescription
dry_runboolean––
project_dirstringyes–

No output schema declared.

No examples provided.

kage_conflicts ~53

List repo-local memory packet pairs that contradict each other (same cited path, same subject, opposing claim). Resolve each with kage_supersede, or keep both intentionally.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_context ~175

Primary kage entry point. Validates memory health, recalls relevant packets, and queries both the code graph and knowledge graph — all in one call. Call this at the start of every task instead of calling kage_validate, kage_recall, kage_code_graph, and kage_graph separately.

NameTypeReqDescription
changed_filesarray–Optional changed files for pre-edit or PR risk context
limitnumber–Max memory packets to return (default 5)
project_dirstringyesAbsolute path to the project root
querystringyesThe task or question — used for both memory recall and code graph search
session_idstring–Optional active agent session id for memory reconciliation
targetsarray–Optional files the agent may edit or explain; used for risk context

No output schema declared.

No examples provided.

kage_context_slot_delete ~35

Delete a repo-local context slot by label.

NameTypeReqDescription
labelstringyes–
project_dirstringyes–

No output schema declared.

No examples provided.

kage_context_slot_set ~98

Create or update a repo-local pinned context slot. Use for durable, high-signal repo guidance that should always be included without loading all memory.

NameTypeReqDescription
contentstringyes–
descriptionstring––
labelstringyes–
pathsarray––
pinnedboolean––
project_dirstringyes–
size_limitnumber––
tagsarray––

No output schema declared.

No examples provided.

kage_context_slots ~46

List repo-local pinned context slots. Pinned slots are small, reviewable facts that Kage includes in recall/context before task-specific memory.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_contributors ~48

Build local contributor profiles from git history: commits, recent activity, touched files, modules, ownership silos, hotspot ownership, and commit category mix.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_decisions ~60

Summarize Kage why-memory for a repo: decisions, gotchas, runbooks, conventions, code explanations, path coverage, weak/stale memory, and important code paths that still lack decision memory.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_dependency_path ~74

Find how two files are connected in Kage's source-derived code graph. Reports direct dependency direction, reverse impact direction, or undirected graph connection.

NameTypeReqDescription
fromstringyesSource file path or unique suffix
project_dirstringyes–
tostringyesTarget file path or unique suffix

No output schema declared.

No examples provided.

kage_distill ~48

Distill stored observations for one session into repo-local memory candidates. Org/global promotion still requires explicit human review.

NameTypeReqDescription
project_dirstringyes–
session_idstringyes–

No output schema declared.

No examples provided.

kage_docs_search ~109

Search this repo's OWN committed documentation (README, docs/**, *.md, common doc dirs — including any framework/API docs checked into the repo). BM25 over heading-anchored chunks from .agent_memory/indexes/docs-index.json. Returns ranked doc hits with doc_path, heading, line, and snippet. This indexes only files on disk in the project, never the internet.

NameTypeReqDescription
limitnumber––
project_dirstringyes–
querystringyes–

No output schema declared.

No examples provided.

kage_feedback ~50

Record usefulness feedback on an approved repo-local memory packet: helpful, wrong, or stale.

NameTypeReqDescription
kindstringyes–
packet_idstringyes–
project_dirstringyes–

No output schema declared.

No examples provided.

kage_fetch ~90

Fetch the full content of a specific node from the kage knowledge graph. Use after kage_search to get the complete fix, pattern, or decision.

NameTypeReqDescription
domainstringyesThe domain the node belongs to, e.g. 'database', 'auth', 'payments'
node_idstringyesThe node slug, e.g. 'prisma-serverless-connection-exhaustion'

No output schema declared.

No examples provided.

kage_graph ~55

Query the repo-local Kage knowledge graph. Returns typed, evidence-backed graph facts from entities, edges, and episodes.

NameTypeReqDescription
limitnumber––
project_dirstringyes–
querystringyes–

No output schema declared.

No examples provided.

kage_graph_insights ~54

Return deterministic code graph intelligence: central files, dependency cycles, import communities, and short entry flows. Use to orient agents before broad architectural edits.

NameTypeReqDescription
project_dirstringyesAbsolute path to the project root

No output schema declared.

No examples provided.

kage_graph_registry ~73

Build a signed graph-registry manifest for generated memory graph, code graph, indexes, metrics, audit, inbox, source packet IDs, packet hashes, and repo git state.

NameTypeReqDescription
fullboolean–Force a full code graph rebuild instead of reusing unchanged graph artifacts.
project_dirstringyes–

No output schema declared.

No examples provided.

kage_graph_visual ~42

Export the repo-local Kage knowledge graph as Mermaid flowchart text for visual inspection.

NameTypeReqDescription
limitnumber––
project_dirstringyes–

No output schema declared.

No examples provided.

kage_inbox ~44

Return an actionable memory review inbox: pending packets, stale packets, duplicates, missing structured context, validation issues, and recommended actions.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_install_policy ~37

Install or update the repo AGENTS.md policy that tells coding agents to use Kage automatically.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_learn ~194

Capture an actual reusable learning from the current session as repo-local memory. Prefer this over diff proposal when the agent knows what was learned. Capture is rejected if every referenced path is missing from the repo; set allow_missing_paths to record anyway (e.g. a file you are about to create).

NameTypeReqDescription
allow_missing_pathsboolean––
discovery_tokensnumber–Approximate token cost of producing this knowledge (exploration + reasoning). Stored on the packet so recall receipts can report replay value; a conservative per-type default is estimated when omitte…
evidencestring––
graph_nodesarray––
learningstringyes–
pathsarray––
project_dirstringyes–
stackarray––
tagsarray––
titlestring––
typestring––
verified_bystring––

No output schema declared.

No examples provided.

kage_learning_ledger ~61

Return an agent-facing ledger that classifies observed session events into save, ignore, needs-evidence, or already-distilled memory decisions.

NameTypeReqDescription
limitnumber––
project_dirstringyes–
session_idstring––

No output schema declared.

No examples provided.

kage_list_domains ~33

List all domains in the kage knowledge graph with their node counts and top tags. Use to orient before searching.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

kage_memory_access ~45

Report which repo-local memory packets have actually been recalled recently. This uses local ignored access telemetry and does not mutate shareable packet files.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_memory_audit ~53

Return the repo-local audit trail for explicit memory mutations: capture, feedback, review, supersede, deprecate, and delete.

NameTypeReqDescription
limitnumber––
project_dirstringyes–

No output schema declared.

No examples provided.

kage_memory_handoff ~45

Return a teammate/agent handoff queue by combining memory inbox, lifecycle, audit, timeline, and lineage into concrete next actions.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_memory_lifecycle ~50

Return a repo-local memory lifecycle report: healthy, hot, cold, stale, disputed, ungrounded, pending, generated, and concrete review actions.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_memory_lineage ~39

Return memory supersession chains so agents can use current replacement packets and keep retired memory as audit history.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_memory_reconcile ~65

Return agent-owned memory reconciliation work when source files linked to existing memory changed. Agents must update, supersede, or mark stale memory before final handoff.

NameTypeReqDescription
limitnumber––
project_dirstringyes–
session_idstring––

No output schema declared.

No examples provided.

kage_memory_timeline ~49

Return recent repo-memory activity for teammate handoff: added, updated, pending, and deprecated packets with review actions.

NameTypeReqDescription
daysnumber––
project_dirstringyes–

No output schema declared.

No examples provided.

kage_metrics ~51

Return concise Kage adoption and quality metrics: code graph counts, language/parser coverage, memory graph evidence coverage, pending/approved packets, validation state, and readiness score.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_module_health ~44

Return local module health scorecards from Kage's code graph, test signals, cleanup candidates, git churn, and ownership concentration.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_observe ~124

Store an automatic local observation event from an agent session. Observations are privacy-scanned, deduplicated, and never published automatically.

NameTypeReqDescription
agentstring––
commandstring––
exit_codenumber––
metadataobject––
pathstring––
project_dirstringyes–
session_idstring––
summarystring––
textstring––
timestampstring––
toolstring––
typestringyes–

No output schema declared.

No examples provided.

kage_pr_check ~59

Check whether repo memory, code graph, memory graph, and stale-memory state are ready for merge. Leads with a human summary of team memories invalidated by the current change — relay it to the developer.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_pr_summarize ~49

Create a PR/branch memory summary from local git diff metadata and write repo-local change memory. Use when a branch is ready to hand off.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_profile ~50

Return a compact project profile for agent orientation: repo totals, languages, top code+memory concepts, key files, memory focus, run commands, and next actions.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_propose_from_diff ~50

Create or update a branch review summary and repo-local change-memory packet from local git status and diff metadata. Org/global promotion still requires explicit human review.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_quality ~45

Return memory quality metrics: useful memory ratio, duplicate burden, stale/wrong feedback, evidence coverage, path grounding, and review queue size.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_recall ~142

Recall repo-local Kage memory from .agent_memory packets. Returns an agent-ready context block plus ranked packet summaries.

NameTypeReqDescription
docsboolean–If true, append a Docs section (<=3 hits) drawn from this repo's own committed documentation.
embeddingsboolean––
explainboolean––
jsonboolean––
limitnumber––
max_context_tokensnumber––
project_dirstringyes–
querystringyes–
structural_hopsnumber–If >0, append a bounded N-hop code-graph blast radius seeded from the recalled memory's files.

No output schema declared.

No examples provided.

kage_refresh ~106

Rebuild repo indexes, code graph, memory graph, metrics, and stale-memory metadata. Agents should run this after meaningful file/content changes before PR checks; push-only or same-tree commits do not need another refresh. On non-default git branches metadata-only packet rewrites are skipped (quiet refresh) to avoid merge conflicts; pass force to persist them anyway.

NameTypeReqDescription
forceboolean–Persist packet metadata rewrites even on a non-default branch
project_dirstringyes–

No output schema declared.

No examples provided.

kage_registry_recommend ~44

Recommend documentation packs, skills, and optional MCPs for this repo based on its package metadata. Recommendations never install anything automatically.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

kage_review_artifact ~35

Create a Markdown review artifact summarizing pending memory packets for PR or human review.

NameTypeReqDescription
project_dirstringyes–

No output schema declared.

No examples provided.

Common questions

What is the com.kage-core/kage MCP server?

com.kage-core/kage is an MCP server listed in the public MCP registry as com.kage-core/kage. Verified memory for coding agents: claims cited against code, stale withheld, savings receipts. This page covers its npm package (@kage-core/kage-graph-mcp).

Is the com.kage-core/kage MCP server safe to use?

com.kage-core/kage scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. 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 com.kage-core/kage MCP server expose?

com.kage-core/kage exposes 66 tools: kage_context, kage_search, kage_fetch, kage_list_domains, kage_recall, and 61 more. Their descriptions and schemas cost roughly 4,519 tokens of context every time the server is loaded.

Is the com.kage-core/kage MCP server still maintained?

com.kage-core/kage is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the com.kage-core/kage MCP server under?

com.kage-core/kage declares the GPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.