[OlyaTi]

Adds Mnemoverse to data/projects.json under the memory category and regenerates README.md with node scripts/generate-readme.js. The entry renders as the last line of the Memory Systems block because the block is sorted by stars. node scripts/validate.js passes.

mnemoverse/mcp-memory-server is persistent memory for AI agents over MCP. It runs as a hosted remote server with OAuth at https://mcp.mnemoverse.com/mcp, or locally with npx -y @mnemoverse/mcp-memory-server and an API key. The distinguishing mechanism is a feedback signal on recall: the agent reports whether a recalled memory helped or misled, and the server uses that report when it ranks the next recall. The MCP server and the Python SDK are MIT. The engine is hosted, with a free tier. The server is listed in the official MCP Registry. Paper: https://arxiv.org/abs/2603.08965.

On traction: the repository has 21 stars today, below the 50 minimum, so this PR asks for the documented exception for novel projects on the strength of the feedback-ranked recall described above. If the exception does not apply, please close and I will come back once the count is there.

Checklist

• Project added to data/projects.json with correct schema
• node scripts/generate-readme.js was run and README.md is up to date
• node scripts/validate.js passes
• Project meets inclusion criteria (open source: MIT; active: commits this week; documented: README and docs; 21 stars, novelty exception requested above)
• Category and cross-list scope are correct; any duplicate listing is justified (memory only; not submitted to awesome-agent-swarm)
• Description is concise, objective, starts with a capital letter, and ends with punctuation
• Links, paper, license, and factual claims were checked against primary sources
• No duplicate entries

Category

• Memory Systems

Disclosure: I work on Mnemoverse.

---

Note

Low Risk
Documentation and curated JSON only; no executable code or infrastructure changes.

Overview
Adds Mnemoverse (mnemoverse/mcp-memory-server) to the awesome list as a Memory Systems entry in data/projects.json, including metadata (MCP/open-source/memory tags, 21 stars, arXiv paper link) and a short blurb about MCP-based persistent memory with feedback-driven recall re-ranking.

Regenerates the Memory Systems block in README.md so Mnemoverse appears in the star-sorted list (currently last in that section). No runtime or application code changes.

^{Reviewed by Cursor Bugbot for commit 40fd2a2. Bugbot is set up for automated code reviews on this repo. Configure here.}

[autogame-17]

Reviewed the current head 40fd2a282a83a47ebc8d84587c4e33eeae18e947 against the live canonical repository and current upstream main (c50351fb0f08890bc8c01dbe91c681e4d536b34f). The untouched PR passes local validation for 120 projects across 10 categories, and two generator passes preserve the committed README.

Please refresh this branch and resolve the conflict in data/projects.json before another review. This is reproducible without changing a working tree:

git merge-tree --write-tree c50351fb0f08890bc8c01dbe91c681e4d536b34f 40fd2a282a83a47ebc8d84587c4e33eeae18e947

It exits 1 with CONFLICT (content): Merge conflict in data/projects.json. Preserve the current main catalog, apply the Mnemoverse addition once, then regenerate rather than hand-editing the automatic README block. A valid old-head snapshot does not establish that the entry integrates with current main.

The project URL is accessible, active, and neither archived nor disabled. Its MCP server is MIT-licensed; the backing memory engine is hosted, as the PR body and upstream README disclose. The requested below-50-star novelty exception remains a maintainer curation decision (26 stars at this check), not a broken-link issue. The arXiv URL resolves to the SLoD abstraction-discovery paper linked by the upstream project; it is related research, not an evaluation of feedback-ranked memory recall.

After resolving the conflict, run:

node scripts/generate-readme.js
node scripts/validate.js
git diff --check
node scripts/check-links.js

Actual successful validation/link workflow checks are still required before approval. This comment does not approve inclusion, approve workflow execution, or merge the PR.

[cursor]

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.

[autogame-17]

Verified the refreshed catalog-only diff against current main. The objective feedback-reranking MCP description is retained; the unrelated knowledge-graph paper field is removed and the canonical star snapshot refreshed. Generated README, validation, and link checks passed locally and in the two current GitHub Actions jobs.