MCP.Market

ProjectKeeper MCP server

by feiyanglyy-stack·io.github.feiyanglyy-stack/projectkeeper·v1.0.0·2 stars

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

B74/100grade B
What users say
No reviews yet
Be the first
Safety scan
B74/100

full report

Adoption
Growing

2 stars

Reviews

Write one

Nobody has reviewed ProjectKeeper yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

ProjectKeeper tools (5)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • projectkeeper_ask

    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.

  • projectkeeper_check_table

    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.

  • projectkeeper_context

    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.

  • projectkeeper_get

    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.

  • projectkeeper_options

    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.

Public scan report

scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it

2 medium
  • Code scan236 source files scanned15/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10

Findings (2)

  • mediumnpm install lifecycle script presentinstall.script
  • mediumnpm install lifecycle script presentinstall.script
    package.json: …tack/projectkeeper", "scripts": { "postinstall": "node bin/postinstall.mjs", "start"…
Overall 74/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How ProjectKeeper compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
74/100
higher than 40% of 48,255 servers
Tools
5
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
2
more than 75% of 28,688 servers

What its tools let an agent do: 5 read

Install ProjectKeeper in Claude Code, Cursor or VS Code

Runs npx -y projectkeeper on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add projectkeeper -- npx -y projectkeeper
Add to Cursor

What the publisher says

From the ProjectKeeper repository's README, as published. We do not edit it. Read it on GitHub

ProjectKeeper

AI writes code faster every week. Do you still know whether what it built is what you wanted?

ProjectKeeper puts what you asked for, the decisions you changed and the work the AI actually finished on one map, shows you where they part, and lets the next agent pick up where the last one stopped — even on a project left half-done. Your own agent takes the project over by reading it as it is and filling in one table; from then on a resident agent keeps the map current every day.

  • Anchored to what you said. Your words are kept verbatim, with the session they were said in. Where a document has drifted from them, where something you wanted was dropped along the way, or where work grew that you never asked for, ProjectKeeper tells you.
  • A half-done project, ready to hand over. Point it at the folder: documents, git history, code and agent sessions become one picture, and one command gives the next agent the context for the work it picks up.

English · 简体中文

One real project on one screen: what the owner asked for, the goals and product areas, two earlier plans, and the current plan's work. Every object opens to its sources.

Why

Let AI build a piece of software for long enough and you end up here: the conversations pile up, the plan keeps changing, and the agents have been swapped several times. Every agent says its task is done, yet nobody can say in full what was asked for at first, what changed later, and what was finally built. The answers exist — in documents, commit messages and session logs nobody will read again.

ProjectKeeper works like a project's archivist. It does not write code for the agents; it lines up every request, every change and the work actually finished. Where they do not match, it tells you; when the agent changes, it hands the whole story to the next one.

It is not too late to bring it in halfway: it goes through the sessions, documents and commits already there, and tells you what each version of the requirements was, what it was changed to, and which version is the one built. All of it happens on your machine.

What you get

  • The whole project on one map. What you said you wanted, the goals, the product areas, the plans, and each piece of work in its place.
  • What really happened to each piece of work. Its steps — dispatched, delivered, reviewed, fixed, merged — each with the commit, report or verdict it rests on, and marked Inferred where the Keeper inferred it.
  • Where a decision came from. Your own words, quoted verbatim with the session they were said in, and the documents and commits that carried the decision on.
  • What became of old plans. Every item of an earlier plan with what happened to it: carried on, moved, deferred or dropped.
  • What needs you. Notes that ask for your decision and give options, and send-backs — a review that failed and nobody picked up — ready to copy to an agent.
  • The right context for the next agent. One command gives an agent the pack for a work item: what it serves, how it got here, your project's rules, where the code is.

And it stays current: after the takeover, a round runs on the schedule you set, or when you press Follow up.

After one pass

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

ProjectKeeper: common questions

Is ProjectKeeper MCP server safe?
Mostly: it is graded B (74/100). Read the ProjectKeeper safety report
How do I install ProjectKeeper?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does ProjectKeeper need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is ProjectKeeper maintained?
The last commit was 19 days ago (2026-10-16). The latest release is v1.0.0.
How does ProjectKeeper compare with other MCP servers?
safety score 74/100 (higher than 40% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.