com.kage-core/kage
NPM · @KAGE-CORE/KAGE-GRAPH-MCP · SCANNED AUG 3
Verified memory for coding agents: claims cited against code, stale withheld, savings receipts.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (98 of 102), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (98 of 102), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (GPL-3.0-only).Pass
- Actively maintained (last published 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability43
- AI-judged instruction clarity (poor).Fail
- 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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @kage-core/kage-graph-mcp
claude mcp add com-kage-core-kage -- npx -y @kage-core/kage-graph-mcp
codex mcp add com-kage-core-kage -- npx -y @kage-core/kage-graph-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-kage-core-kage": {
"type": "local",
"command": [
"npx",
"-y",
"@kage-core/kage-graph-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-kage-core-kage --command npx --arg -y --arg @kage-core/kage-graph-mcp
mcp_servers:
com-kage-core-kage:
command: "npx"
args: ["-y", "@kage-core/kage-graph-mcp"] {
"mcpServers": {
"com-kage-core-kage": {
"command": "npx",
"args": [
"-y",
"@kage-core/kage-graph-mcp"
]
}
}
} 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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +33
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.23 ▲ functional
- License: unverified → pass ▲ functional
- Licence: GPL-3.0-only functional
- 1 Aug 26 +17
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Dependency health: partial → unverified ▼ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 31 Jul 26 +3
- 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 −61
- Known CVEs: partial → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Maintenance: pass → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- License: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Licence: GPL-3.0-only functional
- 28 Jul 26 +25
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Schema quality: unverified → poor ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Licence: GPL-3.0-only functional
- 27 Jul 26 42
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@kage-core/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 98 packages
98 packages in the resolved dependency tree · 97 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
kage_reviewers ~85
Suggest reviewers for target or changed files from local git authorship, recent edits, and code-graph co-change ownership. Does not contact GitHub or external services.
| Name | Type | Req | Description |
|---|---|---|---|
| changed_files | array | — | Optional PR/branch changed files. If targets is omitted, these are used. |
| project_dir | string | yes | — |
| targets | array | — | File paths to review |
No output schema declared.
No examples provided.
kage_risk ~94
Assess modification risk for files using Kage's code graph plus local git history: dependents, impact surface, churn, ownership, co-change partners, and test gaps. Use before editing hotspot or shared files.
| Name | Type | Req | Description |
|---|---|---|---|
| changed_files | array | — | Optional PR/branch changed files. If targets is omitted, these are assessed. |
| project_dir | string | yes | — |
| targets | array | — | File paths to assess |
No output schema declared.
No examples provided.
kage_search ~138
Search the kage community knowledge graph for gotchas, patterns, configs, and architectural decisions across auth, database, payments, deployment, frontend, testing, and more. Returns node summaries ranked by relevance.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | — | Optional: restrict search to a specific domain. One of: auth, database, payments, deployment, frontend, testing, api-design, email, storage, ai-agents, security, performance, observability, infrastru… |
| query | string | yes | What you are looking for, e.g. 'prisma serverless connection', 'stripe webhook signature', 'JWT refresh token' |
No output schema declared.
No examples provided.
kage_session_replay ~65
Return a privacy-preserving replay digest for observed agent sessions: timeline, touched paths, commands, durable candidates, and distill actions without raw transcript text.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | — |
| project_dir | string | yes | — |
| session_id | string | — | — |
No output schema declared.
No examples provided.
kage_sessions ~40
Summarize local agent observation sessions, durable capture candidates, and next distillation actions without exposing raw transcript replay.
| Name | Type | Req | Description |
|---|---|---|---|
| project_dir | string | yes | — |
No output schema declared.
No examples provided.
kage_setup_agent ~76
Generate MCP/setup instructions for Codex, Claude Code, Cursor, Windsurf, Gemini CLI, OpenCode, Cline, Goose, Roo Code, Kilo Code, Claude Desktop, Aider, or generic MCP.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | — |
| project_dir | string | yes | — |
| write | boolean | — | — |
No output schema declared.
No examples provided.
kage_setup_doctor ~36
Audit Kage setup across supported agents, including Claude Code ambient hook readiness when applicable.
| Name | Type | Req | Description |
|---|---|---|---|
| project_dir | string | yes | — |
No output schema declared.
No examples provided.
kage_structural_index ~52
Build the complete cache-backed structural index for large repos. This covers all supported source/config/doc files and writes .agent_memory/structural artifacts separate from learned memory.
| Name | Type | Req | Description |
|---|---|---|---|
| project_dir | string | yes | — |
No output schema declared.
No examples provided.
kage_supersede ~63
Mark one repo-local memory packet as superseded by a replacement packet and write bidirectional lineage edges.
| Name | Type | Req | Description |
|---|---|---|---|
| packet_id | string | yes | — |
| project_dir | string | yes | — |
| reason | string | — | — |
| replacement_packet_id | string | yes | — |
No output schema declared.
No examples provided.
kage_validate ~36
Validate repo-local Kage memory packets, pending packets, generated indexes, and sensitive-content checks.
| Name | Type | Req | Description |
|---|---|---|---|
| project_dir | string | yes | — |
No output schema declared.
No examples provided.
kage_verify_agent ~57
Verify that Kage is truly active for the current agent: config, repo policy, indexes, recall, code graph, and this live MCP tool reachability.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | — |
| project_dir | string | yes | — |
No output schema declared.
No examples provided.
kage_verify_citations ~75
Verify that a memory packet's cited file paths still exist and that the memory is not stale, before trusting it. Pass an id to check one packet, or omit to audit all approved repo memory. Returns grounding and staleness for each.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | — | — |
| project_dir | string | yes | — |
No output schema declared.
No examples provided.
kage_workflow ~204
Kage memory workflow (this tool performs no action; it returns this loop). 1) Start every task with kage_context (project_dir + the task as query): it validates memory, recalls relevant packets, and queries the code and knowledge graphs in one call. 2) Do the work, preferring repo memory over public context. 3) Capture reusable learnings with kage_learn — bug causes and verified fixes, conventions, decisions, gotchas, run/test/build commands. Wrap anything that must never leave the repo in <private>...</private> tags; private spans are stripped before sharing. 4) After meaningful file changes, call kage_refresh so indexes, graphs, and stale-memory checks stay current. 5) Before finishing a branch, call kage_pr_summarize then kage_pr_check. Recall receipts show estimated tokens saved versus rediscovery; report memory quality with kage_feedback (helpful/wrong/stale).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
kage_workspace ~77
Summarize a local multi-repo workspace: discovered git repos, Kage memory coverage, code graph counts, package dependencies, route contracts, topic/event contracts, and cross-repo co-change links between repos. Use when a task spans multiple sibling repos.
| Name | Type | Req | Description |
|---|---|---|---|
| project_dir | string | yes | Workspace root directory to scan for git repos |
No output schema declared.
No examples provided.
kage_workspace_recall ~86
Recall Kage memory across every indexed repo in a local workspace and rank the combined hits. Use for cross-repo teammate knowledge and shared context.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max combined hits to return (default 8) |
| project_dir | string | yes | Workspace root directory to scan for git repos |
| query | string | yes | Question or task to recall across repos |
No output schema declared.
No examples provided.
kage_xray ~47
Return a first-use Repo X-Ray: code structure layers for entry points, core files, risk, tests, memory overlay, and knowledge gaps.
| Name | Type | Req | Description |
|---|---|---|---|
| project_dir | string | yes | — |
No output schema declared.
No examples provided.