io.github.ldclabs/KIP
NPM · @LDCLABS/KIP-MCP-SERVER
Knowledge Graphs to enable memory persistence, knowledge evolution, explainable interaction.
Available components
Last scanned (3 hours ago)
Scores higher than 77% of npm servers
Category Memory and Knowledge
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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency31
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 287 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 483 tokens (~120/item across 4 items; 2 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 3 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
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.
- 4 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.97 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 22 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
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 5 Nov 2026 · Analysed npm/@ldclabs/kip-mcp-server@1.0.1
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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
execute_kip Execute KIP Commands ~384
Execute KIP (Knowledge Interaction Protocol) commands against a Cognitive Nexus backend. IMPORTANT: KIP is new and typically NOT present in the model's training data. Before using this tool for anything non-trivial (especially writes), you MUST load KIP usage instructions. Do one of the following first: - Use the prompt: kip_bootstrap (recommended) - Or fetch the resources: kip://docs/Instructions.md and (optionally) kip://docs/KIP.md Input shape: - Provide exactly one of: 'command' (single multi-line string) OR 'commands' (batch). - Use 'dry_run: true' to validate without executing. Schema grounding (do not guess): - Types are UpperCamelCase; predicates/attributes are snake_case (case-sensitive). - If unsure about schema/types/predicates, discover first via META: DESCRIBE / SEARCH. Safe parameterization: - Prefer 'parameters' over string interpolation. - Placeholders start with ':' and MUST occupy a complete JSON value token. Update semantics: - SET ATTRIBUTES overwrites each specified key (arrays/objects are replaced, not merged). - SET PROPOSITIONS is additive (creates/updates links). Safety: - Never store secrets/credentials or one-time tokens in KIP.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | – | A complete, multi-line KIP command (KQL, KML or META) string to be executed. Mutually exclusive with 'commands'. |
| commands | array | – | Batch execution: array of KIP commands. Mutually exclusive with 'command'. Strings use shared 'parameters'; objects can override 'parameters'. |
| dry_run | boolean | – | If true, validate only without execution. |
| parameters | object | – | Optional key-value pairs used for safe substitution of placeholders in command(s). Placeholders start with ':' and must occupy a complete JSON value token. |
No output schema declared.
No examples provided.
list_logs List KIP Logs ~65
List log entries from the KIP backend (if supported). Use this to debug failed executions or inspect recent activity.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Optional pagination cursor. |
| limit | integer | – | Maximum number of log entries to return (default: 10, max: 100). |
No output schema declared.
No examples provided.
How do I install the io.github.ldclabs/KIP MCP server?
io.github.ldclabs/KIP runs locally as an npm package, launched with npx -y @ldclabs/kip-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @ldclabs/kip-mcp-server
claude mcp add ldclabs-kip -- npx -y @ldclabs/kip-mcp-server
What is the io.github.ldclabs/KIP MCP server?
io.github.ldclabs/KIP is an MCP server listed in the public MCP registry as io.github.ldclabs/KIP. Knowledge Graphs to enable memory persistence, knowledge evolution, explainable interaction. This page covers its npm package (@ldclabs/kip-mcp-server).
Is the io.github.ldclabs/KIP MCP server safe to use?
io.github.ldclabs/KIP scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 io.github.ldclabs/KIP MCP server expose?
io.github.ldclabs/KIP exposes 2 tools: execute_kip, list_logs. Their descriptions and schemas cost roughly 449 tokens of context every time the server is loaded.
Is the io.github.ldclabs/KIP MCP server still maintained?
io.github.ldclabs/KIP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.