@kaaustubh/project-memory-mcp

MCPcommunity
v1.6.0io.github.kaaustubhUnknownUpdated 3mo agonpmGitHub

Persistent memory for AI coding agents — past bugs, decisions, and your corrections, in your repo.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3mo agoLast update
Package
Authorio.github.kaaustubh
LicenseUnknown
Version1.6.0
Sourcenpm+mcp-registry
npm@kaaustubh/project-memory-mcp
GitHubkaaustubh/project-memory-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface16 tools · none privileged
Security scan✓ Cleanv1.10.0 · 2mo agoHow well does this scan work?
EvalsNone
IndexedJul 3, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

16 tools · none privileged
Statically extracted from the published packagev1.10.0 · 2mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_projectsNo description published

This tool published no description. Forge does not invent one.

get_projectNo description published

This tool published no description. Forge does not invent one.

search_memoryNo description published

This tool published no description. Forge does not invent one.

append_decisionNo description published

This tool published no description. Forge does not invent one.

append_learningNo description published

This tool published no description. Forge does not invent one.

remember_preferenceNo description published

This tool published no description. Forge does not invent one.

log_issueNo description published

This tool published no description. Forge does not invent one.

search_issuesNo description published

This tool published no description. Forge does not invent one.

list_open_issuesNo description published

This tool published no description. Forge does not invent one.

resolve_issueNo description published

This tool published no description. Forge does not invent one.

start_initiativeNo description published

This tool published no description. Forge does not invent one.

get_initiativeNo description published

This tool published no description. Forge does not invent one.

list_initiativesNo description published

This tool published no description. Forge does not invent one.

update_initiativeNo description published

This tool published no description. Forge does not invent one.

sync_registryNo description published

This tool published no description. Forge does not invent one.

find_by_fileNo description published

This tool published no description. Forge does not invent one.

0 of 16 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Persistent memory for AI coding agents — past bugs, decisions, and your corrections, in your repo.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

16 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in memory & knowledge graphs