# io.github.neverinfamous/memory-journal-mcp

Developer journal with knowledge graphs, relationships, Git context, and semantic search

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.1.3
- **Author:** io.github.neverinfamous
- **License:** Unknown
- **Source:** https://github.com/neverinfamous/memory-journal-mcp.git

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-06T21:18:09.077Z
- **Version scanned:** HEAD
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

40 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `adversarial-plan-review` — Bootstrap an adversarial planning workflow with structured review dimensions, scoring rubric, and prior plan context from the journal
- `topic` — The feature, change, or system being planned (used to search for prior plans)
- `depth` — Review depth: "light" (correctness + security only), "standard" (all 5 dimensions), or "deep" (extended analysis). Default: standard
- `project-status-summary` — GitHub Project status reports
- `project_number` — GitHub Project number
- `pr-summary` — Pull request journal activity summary
- `pr_number` — Pull request number
- `code-review-prep` — Comprehensive PR review preparation
- `pr-retrospective` — Completed PR analysis with learnings
- `actions-failure-digest` — CI/CD failure analysis with root cause identification
- `project-milestone-tracker` — Milestone progress tracking
- `flag-dashboard` — Triage active flags with priority assessment and resolution guidance
- `flag_type` — Filter to a specific flag type (e.g., blocker, needs_review). Omit to show all.
- `find-related` — Discover connected entries via semantic similarity
- `query` — Search query for finding related entries
- `prepare-standup` — Daily standup summaries
- `prepare-retro` — Sprint retrospectives
- `days` — Number of days to include (default: 14)
- `weekly-digest` — Day-by-day weekly summaries
- `analyze-period` — Deep period analysis with insights
- `start_date` — Start date (YYYY-MM-DD)
- `end_date` — End date (YYYY-MM-DD)
- `goal-tracker` — Milestone and achievement tracking
- `get-context-bundle` — Project context with recent entries, statistics, and GitHub status hints
- `get-recent-entries` — Formatted recent entries
- `limit` — Number of entries (default: 10)
- `confirm-briefing` — Acknowledge session context received from memory://briefing to inform the user
- `session-summary` — Create a session summary entry capturing what was accomplished, pending items, and context for the next session
- `team-session-summary` — Create a session summary entry for the team capturing what was accomplished, pending items, and context for the next team session
- `update_entry` — Update an existing journal entry (content, type, tags, and 11 metadata fields including significance, project, issue, PR, and workflow). Pass null to clear a fi
- `delete_entry` — Delete a journal entry (soft delete with timestamp). Calling with permanent: true on a previously soft-deleted entry works. Returns success: false for nonexiste
- `merge_tags` — Merge one tag into another to consolidate similar tags (e.g., merge "phase-2" into "phase2"). The source tag is deleted after merge. Only updates non-deleted en
- `rebuild_vector_index` — Rebuild the semantic search vector index from all existing entries
- `add_to_vector_index` — Add a specific entry to the semantic search vector index
- `get_statistics` — Get journal statistics and analytics (Phase 2: includes project breakdown)
- `get_cross_project_insights` — Analyze patterns across all GitHub Projects tracked in journal entries. Use for architecture planning.
- `backup_journal` — Create a timestamped backup of the journal database. Backups are stored in the backups/ directory.
- `list_backups` — List all available backup files with their sizes and creation dates
- `restore_backup` — Restore the journal database from a backup file. WARNING: This replaces all current data. Enforce single-writer / single-instance only for restore-capable deplo
- `cleanup_backups` — Delete old backup files, keeping only the most recent N backups. Use list_backups to preview before cleanup.

## Install

This entry has no npm package and no hosted endpoint, so there is nothing for an MCP client to launch or connect to. It is indexed as source only.

## Blast radius

Moderate to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data.
- Floor 26, ceiling 62 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.neverinfamous%2Fmemory-journal-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.neverinfamous%2Fmemory-journal-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.neverinfamous%2Fmemory-journal-mcp
- HTML page: https://forgeregistry.com/registry/io.github.neverinfamous%2Fmemory-journal-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.