nocturne_memory (Dataojitori/nocturne_memory) is an MCP server listed on the M8ven Trust Index. It scores 98 out of 100, grade A. It declares 8 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
A
Trusted
98/100
1 month ago

nocturne_memory

A lightweight, rollbackable, and visual Long-Term Memory Server for MCP Agents. Say goodbye to Vector RAG and amnesia. Empower your AI with persistent, graph-like structured memory across any model, session, or tool. Drop-in replacement for OpenClaw.

→ Dataojitori/nocturne_memory· listed on github_topic

Trusted. Deep verification, no outstanding findings, and an established reputation. 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

Dataojitori

Source: github_topic

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

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// 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: CF_MAIL_AUTH_TOKEN
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.
configSKIP_FRONTEND_BUILD首次启动时，服务器会自动运行 npm install && npm run build 构建前端（需要 [Node.js](https://nodejs.org/)）。如果自动构建失败，可设置环境变量 =true，然后手动执行：
configSKIP_DB_INIT
config_NOCTURNE_SSE_MODE
configUVICORN_HOST
configAG_CDP_PORT
configAG_HEARTBEAT_INTERVAL
configAG_GENERATION_TIMEOUT
configAG_SCREENSHOT_MODE
configTRUSTED_SENDERS
🔐 secretCF_MAIL_AUTH_TOKEN
configNAMESPACEstdio 模式——通过环境变量 指定：
configNEO4J_URIexport ="bolt://localhost:7687"
configdbuserexport ="neo4j"
configdbpasswordexport ="your_password"
configSNAPSHOT_DIR
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
// 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

8/8 tools missing one or more hints — read_memory (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_memory (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); update_memory (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 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.

Tool test coverage

Only 0/8 tools referenced in tests (0%)

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 3 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/dataojitori/nocturne_memory)](https://m8ven.ai/mcp/dataojitori/nocturne_memory)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 7cd214ff9107ae722555ed8c2688a6922d719e9e
code hash: 08a4e7a3a46dd5b73df1976fa534a3f6c0fcc355904aeb52f99b0a39289d4cc8
verified: 8/7/2026, 2:10:31 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