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

C
Caution
74/100

neverinfamous/memory-journal-mcp

A MCP server built for developers enabling Git based project management with project and personal…

Caution. Specific findings reduced this grade. They are listed on the page. 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

neverinfamous

Source: Official · also listed on 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 →

Install from

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
⚠️
Known vulnerabilities in dependencies: 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
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 3 credentials: GITHUB_TOKEN, GITLAB_API_TOKEN, MCP_AUTH_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 high1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highsimple-git@3.35.2GHSA-hffm-xvc3-vprc

simple-git is vulnerable to Remote Code Execution

lowesbuild@0.28.0GHSA-g7r4-m6w7-qqqr

esbuild allows arbitrary file read when running the development server on Windows

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configALLOWED_IO_ROOTS"": "/app/repo"
configAUDIT_LOG_MAX_SIZE
configAUDIT_LOG_PATH"": "/app/data/mcp-audit.jsonl",
configAUDIT_READS
configAUDIT_REDACT
configAUTO_REBUILD_INDEX"": "true",
configBRIEFING_COPILOT_REVIEWS"": "true",
configBRIEFING_ENTRY_COUNTJournal Content — , BRIEFING_SUMMARY_COUNT, BRIEFING_INCLUDE_TEAM
configBRIEFING_INCLUDE_TEAM"": "true",
configBRIEFING_ISSUE_COUNTGitHub Enrichment — , BRIEFING_PR_COUNT, BRIEFING_PR_STATUS, BRIEFING_MILESTONE_COUNT, BRIEFING_WORKFLOW_COUNT, BRIEFING_WORKFLOW_STATUS, BRIEFING_COPILOT_REVIEWS
configBRIEFING_MILESTONE_COUNTGitHub Enrichment — BRIEFING_ISSUE_COUNT, BRIEFING_PR_COUNT, BRIEFING_PR_STATUS, , BRIEFING_WORKFLOW_COUNT, BRIEFING_WORKFLOW_STATUS, BRIEFING_COPILOT_REVIEWS
configBRIEFING_PR_COUNTGitHub Enrichment — BRIEFING_ISSUE_COUNT, , BRIEFING_PR_STATUS, BRIEFING_MILESTONE_COUNT, BRIEFING_WORKFLOW_COUNT, BRIEFING_WORKFLOW_STATUS, BRIEFING_COPILOT_REVIEWS
configBRIEFING_PR_STATUS"": "true",
configBRIEFING_SUMMARY_COUNTJournal Content — BRIEFING_ENTRY_COUNT, , BRIEFING_INCLUDE_TEAM
configBRIEFING_WORKFLOW_COUNTGitHub Enrichment — BRIEFING_ISSUE_COUNT, BRIEFING_PR_COUNT, BRIEFING_PR_STATUS, BRIEFING_MILESTONE_COUNT, , BRIEFING_WORKFLOW_STATUS, BRIEFING_COPILOT_REVIEWS
configBRIEFING_WORKFLOW_STATUS"": "true",
configCODEMODE_INTERNAL_FULL_ACCESS"": "true",
configCODE_MODE_MAX_RESULT_SIZE
configDB_PATH
configDEFAULT_PROJECT_NUMBER
configFLAG_VOCABULARY
configGITHUB_HOST
🔐 secretGITHUB_TOKEN"": "ghp_your_token_here",
🔐 secretGITLAB_API_TOKEN
configGITLAB_URL
configHOST
configINSTRUCTION_LEVELDepth — : essential, standard (default), or full
configLOG_LEVEL
🔐 secretMCP_AUTH_TOKEN
configMCP_CORS_ORIGIN
configMCP_ENABLE_HSTS
configMCP_HOST
configMCP_URL
configMEMORY_JOURNAL_MCP_TOOL_FILTERControl which tools are exposed via (or CLI: --tool-filter):
configMEMORY_JOURNAL_WORKFLOW_SUMMARY"": "/deploy: prod deployment /audit: security scan",
configOAUTH_ALLOW_PLAINTEXT_LOOPBACK
configOAUTH_AUDIENCE
configOAUTH_CLOCK_TOLERANCE
configOAUTH_ENABLED
configOAUTH_ISSUER
configOAUTH_JWKS_URI
configPROJECT_REGISTRYDynamic Project Routing Switch contexts across multiple repositories using a single server instance via
configPRUNE_IMPORTANCE_THRESHOLD
configPRUNE_OLDER_THAN_DAYS
configPUBLIC_ORIGIN
configRULES_FILE_PATH"": "/app/rules.md",
configSKILLS_DIR_PATH"": "/app/skills",
configTEAM_AUTHOR"": "your_username"
configTEAM_DB_PATHteam 28 CRUD, search, stats, relationships, IO (Markdown import/export), backup, vector search, cross-project insights, matrix, Hush Protocol flags (requires )
configTRUST_PROXY
configWAIT_SECONDS
// quality suggestions

Dependencies

25 dependencies, 1 flagged: @playwright/test

Tool test coverage

22/73 tools referenced in tests (30%)

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

Shell command execution

27 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Production dependencies are patched

0 critical, 1 high severity in production deps — simple-git@3.35.2 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

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 Verified](https://m8ven.ai/badge/mcp/neverinfamous/memory-journal-mcp?variant=verified)](https://m8ven.ai/mcp/neverinfamous/memory-journal-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: f58eb155ec1761a69138f7e1e034b85e95b89f27
code hash: 646832306010108d34a9888f06dc32e3ca9e68d5686ac9797a2f7d4e37aef6c4
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