mcp-memory (sdimitrov/mcp-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
1 month ago

mcp-memory

MCP Memory Server with PostgreSQL and pgvector for long-term memory capabilities

→ sdimitrov/mcp-memory· listed on mcp_so

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

sdimitrov

Source: mcp.so · also listed on github_code

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

mcp.sonot scored hereGitHub

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.
// 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.
configDB_IDLE_TIMEOUT
configDB_MAX_POOL_SIZE
configEMBEDDINGS_MODEL
configEMBEDDINGS_NORMALIZE
configEMBEDDINGS_POOLING
configMCP_DEBUG_LOG_PATH
configMCP_PROTOCOL_VERSION
configMCP_SERVER_DESCRIPTION
configMCP_SERVER_DISPLAY_NAME
configMCP_SERVER_NAME
configMCP_SERVER_PUBLISHER
configMCP_SERVER_VERSION
configSEARCH_DEFAULT_LIMIT
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployPORT
// 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.create (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory.search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); memory.list (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.

License file

No license file

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

Tests exist

No test files found

Add tests that exercise each declared tool.

Dependency freshness

1/3 production deps stale: @xenova/transformers@2024-05-29 (2.2y)

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/sdimitrov/mcp-memory)](https://m8ven.ai/mcp/sdimitrov/mcp-memory)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: d6bcc4a287d21edecc5a536173ec9e823d9a2b64
code hash: 0391f790a07b1e5369be9f412ee7f9bb7fb50910f0830b17827c28124c9aafe0
verified: 8/7/2026, 2:21:55 AM
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