# ProjectKeeper (npm · projectkeeper)

What a project planned, decided and did, for your agents: context packs, notes and the table check.

- Trust score: 67/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `projectkeeper`: 67/100 (this document), [markdown](https://verifymcp.io/servers/feiyanglyy-stack-projectkeeper/projectkeeper.md), [page](https://verifymcp.io/servers/feiyanglyy-stack-projectkeeper/projectkeeper)

## Channel facts

- Registry: `npm`
- Package: `projectkeeper`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 84/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects undici 8.10.2, reached via @earendil-works/pi-coding-agent > undici. A fixed version is available.
  - Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does.
  - 30 of 160 dependencies flagged as unhealthy (1 deprecated).
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 11 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 844 tokens (~168/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the ProjectKeeper MCP server?

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

### Claude

```bash
claude mcp add feiyanglyy-stack-projectkeeper -- npx -y projectkeeper
```

### Cursor

```json
{
  "mcpServers": {
    "feiyanglyy-stack-projectkeeper": {
      "command": "npx",
      "args": [
        "-y",
        "projectkeeper"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "feiyanglyy-stack-projectkeeper": {
      "command": "npx",
      "args": [
        "-y",
        "projectkeeper"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add feiyanglyy-stack-projectkeeper -- npx -y projectkeeper
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "feiyanglyy-stack-projectkeeper": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "projectkeeper"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add feiyanglyy-stack-projectkeeper --command npx --arg -y --arg projectkeeper
```

### Hermes

```yaml
mcp_servers:
  feiyanglyy-stack-projectkeeper:
    command: "npx"
    args: ["-y", "projectkeeper"]
```

### Netclaw

```json
{
  "McpServers": {
    "feiyanglyy-stack-projectkeeper": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "projectkeeper"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add feiyanglyy-stack-projectkeeper -t stdio -c npx -a -y projectkeeper
```

### Other

```json
{
  "mcpServers": {
    "feiyanglyy-stack-projectkeeper": {
      "command": "npx",
      "args": [
        "-y",
        "projectkeeper"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 67, +1)

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

### 2026-11-03 (score 66, +1)

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

### 2026-11-01 (score 65, +1)

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

### 2026-10-31 (score 64, 0)

- [security regression] CVE-2026-118764 affects this package: high

### 2026-10-30 (score 64, +1)

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

### 2026-10-28 (score 63, +1)

- [security regression] CVE-2026-109829 affects this package: high
- [security regression] CVE-2026-109383 affects this package: high
- [security regression] CVE-2026-87029 affects this package: high
- [security regression] CVE-2026-87018 affects this package: high
- [security regression] CVE-2026-109932 affects this package: high

### 2026-10-26 (score 62, +1)

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

### 2026-10-24 (score 61, −2)

- [security regression] CVE-2026-109924 affects this package: high
- [security regression] CVE-2026-109869 affects this package: high
- [security regression] CVE-2026-109841 affects this package: high
- [security regression] Known CVEs: pass → fail

## MCP tools (5)

### `projectkeeper_context` (~239 tokens)

Read-only. The context pack to read before starting work on this project (like `pk context`): purpose and the owner's words, direction, plan, relevant work, recent changes, open notes, with numbered sources. Whole project by default; give `work` for one work item or area.

Input parameters:

- `cwd` (string): A folder inside the project. Default: the folder the server was started in.
- `kind` (string): What the pack is for. Default: Implement.
- `port` (integer): Workbench port. Default: the one in ProjectKeeper's settings (4870).
- `project` (string): Project id (`pk projects` lists them). Default: the project containing cwd.
- `purpose` (string): Start (default for the project) or Work (default with work).
- `recipient` (string): Who reads it: "Incoming agent" (default) or a role the project recognises.
- `since` (string): Time of your last pack; gives only what changed since.
- `work` (string): A work item or area, by id or name. Omit for the whole project.

### `projectkeeper_get` (~167 tokens)

Read-only. Read in full any id a pack names (like `pk get`): a work item or area (its pack), a source src_… (the original; for code, where it is and the version read), a note, a rule, a breakpoint, a send-back, or any other object with its neighbours. Ids, not paths.

Input parameters:

- `cwd` (string): A folder inside the project. Default: the folder the server was started in.
- `id` (string, required): An id from a pack or from projectkeeper_options.
- `port` (integer): Workbench port. Default: the one in ProjectKeeper's settings (4870).
- `project` (string): Project id (`pk projects` lists them). Default: the project containing cwd.

### `projectkeeper_options` (~123 tokens)

Read-only. What can be asked for (like `pk options`): areas and work items with ids and progress, roles, how each pack kind and recipient differs, lit breakpoints, open send-backs, the six things.

Input parameters:

- `cwd` (string): A folder inside the project. Default: the folder the server was started in.
- `port` (integer): Workbench port. Default: the one in ProjectKeeper's settings (4870).
- `project` (string): Project id (`pk projects` lists them). Default: the project containing cwd.

### `projectkeeper_ask` (~180 tokens)

Ask the Keeper about the project (like `pk ask`). Returns what is already organized at once, and an investigation job id; call again with jobId to fetch its answer. Read-only toward the project; the investigation uses the owner's model key.

Input parameters:

- `cwd` (string): A folder inside the project. Default: the folder the server was started in.
- `jobId` (string): An investigation job id from an earlier ask: fetches its answer.
- `port` (integer): Workbench port. Default: the one in ProjectKeeper's settings (4870).
- `project` (string): Project id (`pk projects` lists them). Default: the project containing cwd.
- `question` (string): The question. Not needed with jobId.
- `thread` (string): Keep asking in this thread (from an earlier ask).

### `projectkeeper_check_table` (~135 tokens)

Read-only. Check a filled ProjectKeeper table (like `pk check`): its shape against the schema, its ids and references, and every source against the project's files. Lists every problem, or says there are none. Needs no workbench.

Input parameters:

- `project` (string): The project folder. Default: the folder holding the table's projectkeeper/ folder.
- `sessions` (string): The session-material.jsonl the table quotes the owner from (written by `pk sessions`).
- `table` (string, required): The table file, e.g. projectkeeper/project.json. Relative paths start at the server's folder.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/feiyanglyy-stack-projectkeeper/projectkeeper#diagnostics

## Score history

- 2026-11-05: 67
- 2026-11-04: 66
- 2026-11-03: 66
- 2026-11-02: 65
- 2026-11-01: 65
- 2026-10-31: 64
- 2026-10-30: 64
- 2026-10-29: 63
- 2026-10-28: 63
- 2026-10-27: 62
- 2026-10-26: 62
- 2026-10-25: 61
- 2026-10-24: 61
- 2026-10-23: 63
- 2026-10-22: 63
- 2026-10-21: 63
- 2026-10-20: 68
- 2026-10-19: 67
- 2026-10-18: 67
- 2026-10-17: 66
- 2026-10-16: 66

## Common questions

### What is the ProjectKeeper MCP server?

ProjectKeeper is an MCP server listed in the public MCP registry as io.github.feiyanglyy-stack/projectkeeper. What a project planned, decided and did, for your agents: context packs, notes and the table check. This page covers its npm package (projectkeeper).

### Is the ProjectKeeper MCP server safe to use?

ProjectKeeper scores 67 out of 100 on VerifyMCP. We recorded 9 known advisories against it as of 5 November 2026. 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 ProjectKeeper MCP server expose?

ProjectKeeper exposes 5 tools: projectkeeper_context, projectkeeper_get, projectkeeper_options, projectkeeper_ask, projectkeeper_check_table. Their descriptions and schemas cost roughly 844 tokens of context every time the server is loaded.

### Is the ProjectKeeper MCP server still maintained?

ProjectKeeper 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.

### What licence is the ProjectKeeper MCP server under?

ProjectKeeper declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/projectkeeper
- Socket report: https://socket.dev/npm/package/projectkeeper
- Changelog RSS feed: https://verifymcp.io/servers/feiyanglyy-stack-projectkeeper/projectkeeper.xml
- Changelog JSON feed: https://verifymcp.io/servers/feiyanglyy-stack-projectkeeper/projectkeeper.json
- HTML version of this page: https://verifymcp.io/servers/feiyanglyy-stack-projectkeeper/projectkeeper