Two-tier memory: hot cache (0ms) + semantic search. Self-organizing.
Stop re-explaining your project every session. Memory MCP learns what matters and keeps it ready — instant recall for the stuff you use most, semantic search for everything else. Every new chat starts from scratch. You explain your architecture again. You paste the same patterns again. Your context window bloats with repetition. Other memory solutions help, but they still require tool calls for…
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.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Stop re-explaining your project every session. Memory MCP learns what matters and keeps it ready — instant recall for the stuff you use most, semantic search for everything else. Every new chat starts from scratch. You explain your architecture again. You paste the same patterns again. Your context window bloats with repetition. Other memory solutions help, but they still require tool calls for every lookup — adding latency and eating into Claude's thinking budget. Memory MCP fixes this with a…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.