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

Back to MCP Trust IndexM8ven
C
Emerging
74/100

agent-memory

One memory for every AI agent — self-hosted long-term memory over MCP/REST for Claude Code, Codex, Cursor, Gemini CLI, VS Code, OpenClaw, and more.

→ Masikomoore/agent-memory· listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

Masikomoore

Source: github_repo_search

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

GitHub

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
✅
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 1 credential: OPENAI_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
configCLAWTEAM_MEMORY_SCOPE
configComSpec
configMEMORY_LANCEDB_DISABLE_NATIVE_COSINE
configMEMORY_LANCEDB_REDIS_URL
configMEMORY_PRO_OAUTH_AUTHORIZE_URL
configMEMORY_PRO_OAUTH_CLIENT_ID
configMEMORY_PRO_OAUTH_REDIRECT_URI
configMEMORY_PRO_OAUTH_TOKEN_URL
🔐 secretOPENAI_API_KEY
configOPENCLAW_CLI
configOPENCLAW_CLI_BIN
configOPENCLAW_CONFIG_PATH
configOPENCLAW_HOME
// 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

3/3 tools missing one or more hints — memory_recall (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory_capture (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory_health (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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.

Dependency freshness

2/9 production deps stale: proper-lockfile@2022-06-24 (4.2y), json5@2023-03-04 (3.5y)

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 2 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 Score](https://m8ven.ai/badge/mcp/masikomoore/agent-memory)](https://m8ven.ai/mcp/masikomoore/agent-memory)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 67f7bb644428303bb28d5afc2bbe93441431a37f
code hash: d3bd9a7050410d9aad4e868173a3052109d065077b9c9ea0439487f625d7dde1
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