Clude Memory MCP
v1.0.0MCP server for Clude's 4-tier cognitive memory system — store, recall, search, and dream. Built on Supabase + pgvector with type-specific decay, Hebbian asso...
⭐ 0· 526·0 current·0 all-time
bySebastien Sim@sebbsssss
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
Name/description describe a Supabase + pgvector memory MCP — requiring node and SUPABASE_URL + SUPABASE_SERVICE_KEY is expected. However the code and SKILL.md also reference actions that require additional credentials (Claude API calls, on-chain Solana commits, handling token/tweet events) but no corresponding environment variables are declared. The skill therefore asks for high-privilege DB access while omitting other credentials it clearly needs.
Instruction Scope
SKILL.md instructs installing 'clude-bot' and setting SUPABASE_URL/SUPABASE_SERVICE_KEY, and documents features that will call Claude and commit hashed memories to Solana. The instructions do not disclose that conversational content will be persisted, potentially sent to an LLM (Claude), and committed (hashed) on-chain (which can be irreversible and cost SOL). The runtime code returns full memory content in tool outputs, so sensitive user data could be stored and transmitted; the SKILL.md does not warn or require consent or list additional env keys.
Install Mechanism
There is no automated install spec (lower automated risk). But SKILL.md tells users to run 'npm install clude-bot' — an external package name with no homepage/source in the registry metadata. Installing that package would execute remote code from npm (moderate risk). Also included server.ts imports many local modules (../core/*, ../config) that are not present in the bundle, suggesting incomplete packaging or hidden dependencies that would need to be fetched.
Credentials
The skill requires SUPABASE_SERVICE_KEY: a powerful service_role key that grants full DB access (read/write and bypasses RLS). For a server process this can be justified, but it is high privilege and should be minimized or scoped. The skill also clearly needs other secrets (LLM API key, Solana signer or RPC credentials) that are not declared — omission of these sensitive envs is a mismatch and increases risk because hidden secrets usage could be required or added later.
Persistence & Privilege
The skill does not request 'always: true' and does not appear to change other skills or global agent settings. However it stores persistent user/agent memories in a database and may autonomously commit hashes on-chain and call external LLMs. Autonomous invocation combined with a Supabase service key increases the blast radius if misused — consider restricting runtime privileges and authorizations.
What to consider before installing
This skill is not obviously malicious but has several red flags. Before installing: (1) Do not provide your SUPABASE_SERVICE_KEY unless you trust the code — that key grants full DB access; prefer a scoped DB role. (2) Ask the author for full source for the missing modules (../core/*, ../config) and for a repository/homepage. (3) Clarify where Claude and Solana credentials are expected and what on-chain actions (and fees) will occur; do not use a real wallet/private key in testing. (4) Inspect the npm package 'clude-bot' on the registry before running npm install. (5) Decide if you consent to potentially persisting conversational content and sending it to external services; if not, run in an isolated environment or decline. If the author provides a repo, declared env list updates (including CLAUDE_*/SOLANA_*/RPC variables), and a scoped Supabase role, that would reduce risk; absent that, treat this as suspicious.Like a lobster shell, security has layers — review code before you run it.
latestvk97c8ysvysjgdxqdj3ft2cc4k581pvr8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binsnode
EnvSUPABASE_URL, SUPABASE_SERVICE_KEY
Primary envSUPABASE_URL