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

Back to MCP Trust IndexM8ven
C
Warning
74/100

memory-mcp

Multi-tier memory system for AI assistants, integrating semantic, episodic, time-series, and spatial memory with pattern detection and MCP tools.

→ brianchilders/memory-mcp· listed on glama

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we 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

brianchilders

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
🚨
Code appears obfuscated
2 files are unreadable to a human reviewer. Cannot audit what they do.
🔐
You'll be asked for 5 credentials: MEMORY_AI_API_KEY, MEMORY_LLM_API_KEY, MEMORY_API_TOKEN, HA_TOKEN, MEMORY_MQTT_PASSWORD
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.
configMEMORY_DB_PATH
configMEMORY_AI_BASE_URL
🔐 secretMEMORY_AI_API_KEY
configMEMORY_EMBED_MODEL
configMEMORY_EMBED_DIM
configMEMORY_LLM_MODEL
configMEMORY_LLM_BASE_URL
🔐 secretMEMORY_LLM_API_KEY
configMEMORY_DECAY_HALFLIFE_DAYS
configMEMORY_DECAY_CATEGORY_HALFLIFE
configMEMORY_LOCATION_DECAY_HALFLIFE_HOURS
configMEMORY_AI_TIMEOUTIncrease if using a slow local model. LLM calls use max(, 60)
configMEMORY_LOG_LEVEL
configMEMORY_LOG_FORMAT
🔐 secretMEMORY_API_TOKEN
configMEMORY_CORS_ORIGINS
configHA_URL
🔐 secretHA_TOKEN
configMEMORY_API_URL
configHA_POLL_INTERVAL
configMEMORY_PERSON_NAME
configMEMORY_MQTT_BROKER
configMEMORY_MQTT_PORT
configMEMORY_MQTT_USER
🔐 secretMEMORY_MQTT_PASSWORD
configMEMORY_MQTT_TOPICS
configMEMORY_MQTT_CLIENT_ID
// 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

35/35 tools missing one or more hints — remember (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); recall (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +32 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.

No eval / new Function

2 eval() or new Function() calls — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Readable source code

2 files are minified or bundled, which is usually build output rather than concealment

Ship unminified, readable source.

Secrets not logged

1 secret value sent to log.info

Redact or omit secret values from log output.

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/brianchilders/memory-mcp?variant=verified)](https://m8ven.ai/mcp/brianchilders/memory-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 5671318d66188c310747bab8be34a0e8b905af0a
code hash: 4e2644d3b4a1a9e64fbe9abb329115bd6e73ff1372bdb5d6472bf47c400f51f3
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