ProjectKeeper
NPM · PROJECTKEEPER
What a project planned, decided and did, for your agents: context packs, notes and the table check.
Available components
Last scanned (22 hours ago)
Scores higher than 34% 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 Security84
- No malware found by supply-chain analysis.Pass
- 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. View diagnostics → Fail
- 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. View diagnostics → Partial
- 30 of 160 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 Nov 26 +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.
- 1 Nov 26 +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.
- 31 Oct 26 0
- CVE-2026-118764 affects this package: high ▼ security
- 30 Oct 26 +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.
- 28 Oct 26 +1
- CVE-2026-109829 affects this package: high ▼ security
- CVE-2026-109383 affects this package: high ▼ security
- CVE-2026-87029 affects this package: high ▼ security
- CVE-2026-87018 affects this package: high ▼ security
- CVE-2026-109932 affects this package: high ▼ security
- 26 Oct 26 +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.
- 24 Oct 26 −2
- CVE-2026-109924 affects this package: high ▼ security
- CVE-2026-109869 affects this package: high ▼ security
- CVE-2026-109841 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 0
- Security disclosure: pass → 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 4 Nov 2026 · Analysed npm/projectkeeper@1.0.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 →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | unreviewed | node bin/postinstall.mjs |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 9 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-g3hv-75wg-m249 | CVE-2026-118764 | medium | yes | |
| GHSA-2m5v-pch6-74hx | CVE-2026-109383 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-4qv8-2p9j-2685 | CVE-2026-109924 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-4w7w-5xrc-9h26 | CVE-2026-109829 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-55wc-3pg8-jfw6 | CVE-2026-87029 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-9fm3-97px-rjf6 | CVE-2026-109932 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-f72v-6w45-q472 | CVE-2026-109841 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-qrxm-fqhp-jwvm | CVE-2026-87018 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-xjj6-f33q-929c | CVE-2026-109869 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 160 packages
| Packages resolved | 160 |
|---|---|
| Deprecated | 1 |
| Stale | 29 |
| 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 →
projectkeeper_ask ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
projectkeeper_check_table ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The table file, e.g. projectkeeper/project.json. Relative paths start at the server's folder. |
No output schema declared.
No examples provided.
projectkeeper_context ~239
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
projectkeeper_get ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | A folder inside the project. Default: the folder the server was started in. |
| id | string | yes | 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. |
No output schema declared.
No examples provided.
projectkeeper_options ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
npm · projectkeeper
claude mcp add feiyanglyy-stack-projectkeeper -- npx -y projectkeeper
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 66 out of 100 on VerifyMCP. We recorded 9 known advisories against it as of 4 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 4 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.