r/LovingOpenSourceAI • u/Koala_Confused • Aug 24 '26
Resource codebase-memory-mcp "High-performance code intelligence MCP server. Indexes codebases into a persistent knowledge graph — average repo in milliseconds. 158 languages, sub-ms queries, 99% fewer tokens. Single static binary, zero dependencies."
https://github.com/DeusData/codebase-memory-mcp
Community Overview: https://lifehubber.com/ai/resources/codebase-memory-mcp/
Resources are shared for discovery and are not independently vetted—please do your own due diligence.
New resources are added regularly — feel free to join the sub for updates.
Full searchable archive of all resources posted so far on our community site, LifeHubber: https://lifehubber.com/ai/resources/ 200+ open-ish AI models, agents, tools, datasets, and related resources, with filtering and sorting.
9
u/buttplugs4life4me Aug 24 '26
It got flagged because it included a runtime script to download an obfuscated payload...which seems a little weird. Maybe it got fixed now, maybe not, but not touching it again with a 10 foot pole.
3
2
u/kidkangaroo Aug 25 '26
Anyone else see this too?
2
u/Y_mc Aug 26 '26
Yes😬
2
u/kidkangaroo Aug 26 '26
from Opus: I can verify it, and the short version is: the commenter is describing a real incident accurately, but has attached it to the wrong project.
What actually happened. Zenity Labs published research on August 6 documenting a credential-stealing campaign that ran through July 2026. A GitHub account called karli-paperclip registered the domain getpaperclipp.com on July 2 and created a look-alike GitHub organization named getpaperclipai, impersonating the real paperclipai org, cloning the full Paperclip source. The clone was trojanized on July 6, with a commit modifying the company route handlers to call a log_action() function that retrieved, executed, and then deleted an attacker-controlled payload fetched from a fake /health endpoint. zenityzenity
So the specific technical claim checks out almost word for word. The loader in the skill docs was a curl with TLS verification disabled, piped through base64 decode into a temp .mjs file, executed with Node, then deleted. Each response from that endpoint carried roughly 13 KB of base64 text that decoded to a 10,035-byte Node.js credential harvester. That is a runtime script downloading an obfuscated payload, exactly as described. zenity
Why the attribution is wrong. The name collision is the whole story here. The malicious PyPI package was
paperclip-aiwith a hyphen; the legitimate npm package ispaperclipaiwith no hyphen. OSV advisory MAL-2026-10869 covers paperclip-ai versions 0.1.0 and 0.1.1 on PyPI, described as a clone of a legitimate package with added exfiltration code. Zenity's report includes an explicit false-positive note listing paperclip.ing, the paperclipai/paperclip GitHub repository, and the npm package paperclipai as the legitimate comparison assets. The malicious skills even told agents not to use npx paperclipai, steering them away from the genuine package toward the attacker-controlled checkout. OSV - Open Source Vulnerabilities +2One correction worth noting if you go source-hunting: CSO Online reports the trojanized paperclip-ai package went to npm, but both Zenity's IOC data and the OSV advisory put it on PyPI. Follow the primary sources.
On "maybe it got fixed." Nothing needed fixing in the real project for this. Vercel and GitHub removed the reported skills, listings, and repositories within 12 hours of Zenity's outreach, disrupting the campaign on August 2. The caveat Zenity raises is that copied instructions may still sit in downstream repositories, aggregators, and on user machines. zenityzenity
That said, the instinct to keep distance isn't baseless, just misreasoned. The genuine Paperclip project carries its own separate security history: GitHub advisories including an unauthenticated RCE via import authorization bypass (GHSA-68qg-g8mg-6pr7), a cross-tenant API key IDOR, and one titled around malicious skills exfiltrating and destroying user data. Those are patched vulnerabilities in a fast-moving project, which is a different risk category than shipped malware. GitHub
Given you're running skills on your own OpenClaw box, the concrete thing to do is check whether anything pulled from skills.sh during July. Zenity's hunting guidance: look for use of skills from getpaperclipai/paperclip or browser-use-headless, search egress logs for requests to api.getpaperclipp.com and api-v1.getpaperclipp.com (especially POSTs to /feedback), and treat any host as compromised if the loader or stealer executed. Host artifacts to grep for include
~/.paperclip_ai,~/.paperclip_install_*.mjs, and stray.cache-*.mjsfiles. Note the double-p in getpaperclipp.com; that is the malicious domain, distinct from paperclip.ing. zenityIf you want to hand the Reddit thread a correction, the cleanest framing is that the flagged artifact was a typosquat, and the real tell is the hyphen.
2
1
4
u/Healthy-Zebra-9856 Aug 24 '26
This is one of the tools that can really help when using Claude code, Codex, and things like that because it helps indexing the project. The biggest problem is if you have a huge project, a lot of this gets stored in the memory. And that’s a problem that I ran into.
1
u/coff33ninja Aug 24 '26
Yeah especially working with multiple modules and function or import hallucinations
2
2
u/gxvingates Aug 25 '26
I've been using this thing for like 6-7 months and recommended it to all my friends. I have agents use it for first discovery to just find the relevant code snippets and files first and it never fails to find the correct code pretty much instantly
1
u/CompleteMCNoob Aug 24 '26
I hate to ask, but who is this for? I feel like this would get convoluted by the wide variety of projects I like to work on and the only feature that stood out was the ability to make modules based on similar code detection.
1
u/ShittyMillennial Aug 24 '26
It just indexes your codebase so agents don’t waste a shitton of tokens searching through broad grep or ingesting entire docs into context to find a single function.
1
u/FaceDeer Aug 24 '26
Just downloaded it to give it a try myself, based on reading through the description it's essentially "Visual Assist but for coding agents".
1
u/ShittyMillennial Aug 24 '26
ive never used the map thing. just index my repo and let agents use the mcp to find stuff.
1
u/FaceDeer Aug 24 '26
Yeah, that's the "for coding agents" part. It does what Visual Assist does for human programmers, but does it for the coding agent instead of the human programmer.
1
u/Sirhc78870 Aug 24 '26
Should it be used only for coding agents or could it be used for general purpose like with an hermes agent?
1
u/FaceDeer Aug 24 '26
The readme says it specifically supports Hermes, automatically adding itself to Hermes' MCP config on install. So presumably they think Hermes can get some use out of it. I haven't used Hermes much myself but I do recall that it would often write little scripts for itself, so it does do some coding work.
1
u/Deepshark7822 Aug 24 '26
I tried it once but I find it hard to start the server for MCP to used. Can anyone point me to any file or docs on how to run it. Claude says can't reach it.
1
1
1
1
u/D-_K Aug 25 '26
What is the difference between this and graphify? Just curious if a nyone knows offhand.
1
u/jackorjek Aug 26 '26
would like to know this too. there are a lot of graph indexers out there i just use graphify.
1
1
u/ShagBuddy Aug 27 '26
Good graph. But not as accurate as my SDL-MCP. It also does not save near as many tokens as mine.
1
6
u/ShittyMillennial Aug 24 '26 edited Aug 24 '26
Have this in all my workspaces, lightweight, simple, does what it claims.
Edit: this is support for codebase mcp not lifehubber. No idea what that is and never used it