MemData
v1.8.0Persistent memory for autonomous agents. Wallet = identity. Pay per query. Optional encrypted storage.
⭐ 1· 1.6k·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (persistent memory, wallet identity, pay-per-query) match the SKILL.md: endpoints, pricing, and encrypted-storage flow are all aligned with that purpose. No unrelated env vars, binaries, or install steps are requested.
Instruction Scope
SKILL.md is an instruction-only API spec that tells the agent to call memdata.ai endpoints and to perform a wallet-based x402 payment flow. It does not instruct reading local files or environment variables. It omits low-level details about how to produce the signed payment header or UCAN delegation (it assumes the agent/user will sign via a wallet), which is expected but important to understand.
Install Mechanism
No install spec and no code files — instruction-only skill. This minimizes on-disk risk; nothing is downloaded or installed by the skill itself.
Credentials
The skill declares no required environment variables or credentials, which is consistent with a wallet-based, on-demand signing model. However, practical use requires a wallet/signing capability (private key or wallet integration). The SKILL.md does not request keys directly, so ensure your agent/wallet does not expose private keys to the skill without explicit consent.
Persistence & Privilege
No special persistence flags (always not set). Model invocation is not disabled (default allows autonomous invocation). That is acceptable for a network-based memory API, but because endpoints involve payments, confirm the agent cannot programmatically sign transactions or use stored private keys without explicit interactive approval.
Assessment
This skill appears coherent, but before installing: 1) Verify the service (memdata.ai) and read its docs and privacy policy. 2) Confirm how your agent will sign x402 payments and UCAN delegations — do not allow silent programmatic access to wallet private keys; require interactive signing. 3) Test with a tiny payment to confirm behavior and pricing. 4) If you plan to use encrypted mode, understand the UCAN delegation flow and where the delegationCar is stored. 5) Consider whether you want the agent to be allowed to call this skill autonomously; if not, disable model invocation or require user confirmation for actions that initiate payments.Like a lobster shell, security has layers — review code before you run it.
agentsvk97amv46nwbsx7h949tnn2myb980eyf6autonomousvk97amv46nwbsx7h949tnn2myb980eyf6defivk97amv46nwbsx7h949tnn2myb980eyf6encryptedvk97amv46nwbsx7h949tnn2myb980eyf6latestvk97amv46nwbsx7h949tnn2myb980eyf6memoryvk97amv46nwbsx7h949tnn2myb980eyf6walletvk97amv46nwbsx7h949tnn2myb980eyf6x402vk97amv46nwbsx7h949tnn2myb980eyf6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.