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

Back to MCP Trust IndexM8ven
C
Emerging
74/100

claude-memory

Provides memory and project tracking for Claude Code via MCP, enabling semantic search over past transcripts, durable notes, and structured project management with milestones, epics, tickets, and todos.

→ mathis-sperlich/claude-memory· listed on glama

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

mathis-sperlich

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
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 3 credentials: VOYAGE_API_KEY, QDRANT_API_KEY, GITHUB_CLIENT_SECRET
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.
🔐 secretVOYAGE_API_KEY
configVOYAGE_TIMEOUTStalled embed requests bounded by / VOYAGE_MAX_RETRIES env vars (default 20s / 2).
configVOYAGE_MAX_RETRIESStalled embed requests bounded by VOYAGE_TIMEOUT / env vars (default 20s / 2).
configQDRANT_URL
🔐 secretQDRANT_API_KEY
configQDRANT_COLLECTION
configEMBED_MODELBad results? Lower MAX_CHUNK_CHARS in ingest.py, or try bigger in .env and re-ingest with --reset.
configEMBED_DIM
configGITHUB_CLIENT_ID
🔐 secretGITHUB_CLIENT_SECRET
configBASE_URL
configGITHUB_ALLOWED_USERS
configTOKEN_EXPIRY_SECONDS
configTRACKING_DB
configCLAUDE_PROJECT_DIR
// 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

20/20 tools missing one or more hints — query_history (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_recent_sessions (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); remember (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +17 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

14/20 tools referenced in tests (70%)

Write tests that reference each tool by name so every tool has at least one test.

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 4 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/mathis-sperlich/claude-memory)](https://m8ven.ai/mcp/mathis-sperlich/claude-memory)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 86f8d1ce478449baa8544dd46f3e511f969fe431
code hash: 88d74865fc51bc584a6d6a8fb566667cf7e276878a466745413f1fcc3ae860e4
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