memdata-mcp (thelabvenice/memdata-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 10 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
74/100

memdata-mcp

MCP server for persistent memory, enabling AI agents to store and semantically retrieve notes, decisions, and context across conversations using API keys or x402 payments.

→ thelabvenice/memdata-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

thelabvenice

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: MEMDATA_API_KEY, X402_WALLET_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes10 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

memdata_ingest

Ingest text content into long-term memory for later retrieval. Use this to store important information, notes, decisions, or context that should be remembered across conversations.

memdata_query

Search memory for relevant context based on a natural language query. Returns the most semantically similar stored content with similarity scores.

memdata_list

List all stored memories/artifacts. Shows what content has been ingested with chunk counts and dates. Use this to see what is in memory before querying or to find artifact IDs for deletion.

memdata_delete

Delete a memory/artifact from storage. This permanently removes the content and all associated chunks. Use memdata_list to find artifact IDs.

memdata_status

Check the health and storage usage of your MemData account. Shows API connectivity and how much storage space is used.

memdata_session_start

🚀 CALL THIS FIRST at the start of every session. Returns your identity, what you were working on, last session handoff, recent activity, and memory stats. Essential for session continuity.

memdata_session_end

Save a session handoff before ending. Stores what you were working on and context for the next session. Call this before context compression or when ending a work session.

memdata_set_identity

Set or update your agent identity. Use this to establish who you are and your purpose.

memdata_relationships

Find entities related to a person, company, or concept in your memory. Shows who/what appears together in the same context.

memdata_query_timerange

Search memory within a specific time range. Use for queries like "what did I work on last week" or "meetings from January".

// known CVEs in dependencies1 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.25.3GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretMEMDATA_API_KEYAPI key for subscribers (from memdata.ai)
configMEMDATA_API_URLAPI URL (default: https://memdata.ai)
🔐 secretX402_WALLET_KEYPrivate key for pay-per-use (USDC on Base)
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

10/10 tools missing one or more hints — memdata_ingest (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memdata_query (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memdata_list (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +7 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets not logged

3 secret values sent to error

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@1.25.3 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/thelabvenice/memdata-mcp?variant=verified)](https://m8ven.ai/mcp/thelabvenice/memdata-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 3416989736a40d85f2286c312dc7caba73a69b86
code hash: a313c2f5223ddaedb043c62b89fb823db04f27ccc631fce4bc43665550f9ac0f
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client