npm · server-memory2026.1.26

Evidence

],

  "scripts": {

    "build": "tsc && shx chmod +x dist/*.js",

    "prepare": "npm run build",

    "watch": "tsc --watch",

    "test": "vitest run --coverage"

  },

RemediationAI

The problem is that the 'prepare' script runs `npm run build` automatically whenever the package is installed, executing arbitrary code on every developer's machine and in CI/CD pipelines without explicit user consent. Remove the 'prepare' entry from the scripts object in package.json, or replace it with a no-op script that only documents the build requirement. This eliminates the attack surface where a compromised dependency could execute malicious code during installation by hijacking the prepare hook. Verify the fix by running `npm install` in a clean environment and confirming that the TypeScript compilation does not occur automatically—developers should explicitly run `npm run build` when needed.

Evidence

# Knowledge Graph Memory Server

A basic implementation of persistent memory using a local knowledge graph. This lets Claude remember information about the user across chats.

## Core Concepts

### Entities

Entities are the primary nodes in the knowledge graph. Each entity has:

- A unique name (identifier)

- An entity type (e.g., "person", "organization", "event")

- A list of observations

Example:

```json

{

  "name": "John_Smith",

  "entityType": "person",

  "observations": ["Speaks fluent Span

RemediationAI

The problem is that the MCP manifest does not declare any authentication mechanism, making it unclear whether the knowledge graph server is protected against unauthorized access or if it relies on implicit network isolation. Add an explicit 'auth' or 'authorization' field to the manifest (in the MCP configuration file or README documentation) that clearly states the authentication model—for example, 'auth: "none" (host-level isolation assumed)' or 'auth: "bearer"' if token-based auth is implemented. This remediation allows security reviewers to immediately identify the trust boundary and verify that the server is deployed only in trusted environments or with appropriate access controls. Verify the fix by reviewing the updated manifest alongside your deployment architecture to confirm that the declared auth mechanism matches the actual security posture.