lodekeep

MCPcommunitylive
v0.3.6RodMITUpdated 21d agonpm

Memory MCP server for Claude Code, Cursor and any MCP client. Corrections replace stale facts.

Endpoint healthlive
checked 11 days ago · 54ms · auth required
100% of the last 2 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). 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 →
43Downloads/wk
21d agoLast update
Package
AuthorRod
LicenseMIT
Version0.3.6
Sourcenpm+mcp-registry
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 surface6 tools · none privileged
Security scan✓ Cleanv0.3.6 · 20d agoHow well does this scan work?
EvalsNone
IndexedSep 14, 2026

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

Tools

6 tools · none privileged
Statically extracted from the published packagev0.3.6 · 20d 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.

search_memoryCall this FIRST whenever the user asks about their own past decisions, preferences, project details, codenames, or anything they may have told you before. Semantic search over your curated project memory: finds notes by MEANING using embeddings and vector similarity, so natural-language queries wor…

Call this FIRST whenever the user asks about their own past decisions, preferences, project details, codenames, or anything they may have told you before. Semantic search over your curated project memory: finds notes by MEANING using embeddings and vector similarity, so natural-language queries wor…

No input schema was published for this tool.

get_project_contextLoad a bounded overview of your curated project memory, grouped by project and filtered through your active persona. Returns up to `limit` projects (default 20, max 50), each with a short preview of its notes and its true entry count. This is a summary for orientation, not a full dump of every note.

Load a bounded overview of your curated project memory, grouped by project and filtered through your active persona. Returns up to `limit` projects (default 20, max 50), each with a short preview of its notes and its true entry count. This is a summary for orientation, not a full dump of every note.

No input schema was published for this tool.

get_memory_mapNo description published

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

capture_noteNo description published

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

list_personasList all 5 available coding personas with their quality TARGETS and their effective rigor/security level (each persona shows its full-intensity level and the always-on 40% floor).

List all 5 available coding personas with their quality TARGETS and their effective rigor/security level (each persona shows its full-intensity level and the always-on 40% floor).

No input schema was published for this tool.

set_project_personaValidate and PERSIST your active persona, intensity, and optional blend. Once set, it becomes the DEFAULT persona for your later search_memory and get_project_context calls, until you change it or pass an explicit persona on a call. Enforces plan limits.

Validate and PERSIST your active persona, intensity, and optional blend. Once set, it becomes the DEFAULT persona for your later search_memory and get_project_context calls, until you change it or pass an explicit persona on a call. Enforces plan limits.

No input schema was published for this tool.

4 of 6 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

Memory MCP server for Claude Code, Cursor and any MCP client. Corrections replace stale facts.

Keywords
mcpclaudememorylodekeepcliinstalleranthropic
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-14 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in memory & knowledge graphs