MCP.Market

Living Memory MCP server

online · 100% uptime
by viibe.to·to.viibe/living-memory·v0.1.2·2 stars
No reviews yet

An MCP memory server. One memory your agents share — across models, devices and apps.

A94/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A94/100

full report

Adoption
Growing

2 stars58 downloads/wk

Reviews

Write one

Nobody has reviewed Living Memory yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Living Memory tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • Code scan8 source files scanned25/25
  • Live reliabilityremote reachable in 634ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 32 days ago12/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 94/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Living Memory compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
94/100
higher than 96% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
604 ms
faster than 24% of 30,031 servers
GitHub stars
2
more than 75% of 28,688 servers
Downloads a week
58
more than 48% of 12,191 servers with a package

Install Living Memory in Claude Code, Cursor or VS Code

claude mcp add --transport http living-memory https://lme.viibe.to/mcp
Add to Cursor

What the publisher says

From the Living Memory repository's README, as published. We do not edit it. Read it on GitHub

Living Memory Engine

A persistent world your agents share across sessions and models.

Living Memory Engine (LME) is a Model Context Protocol (MCP) memory server. It gives your agents — Claude Code, Cursor, ChatGPT, claude.ai, any MCP client — one shared place to remember, search, and hand work to each other. A fact told to one agent — or work left behind by one — can be picked up by a different agent, from a different vendor, tomorrow.

  • Website: https://viibe.to/living-memory/
  • Remote MCP endpoint: https://lme.viibe.to/mcp (Streamable HTTP, OAuth 2.1 with dynamic client registration)
  • Free room: no signup — POST https://lme.viibe.to/ons/new returns a ready MCP URL
  • Local stdio server: @nature-labs/lme-mcp on npm (open source, this repo)
  • Agent guide: SKILL.md · llms.txt

The mental model

A world is a place that persists — a project, not a person and not an agent. Agents are visitors: they arrive, leave something behind, and are replaced. Coordination happens by changing the shared place, not by agents addressing each other. Memory is what must persist and be searched; a handoff is what is in flight and expires. The human is the only participant who was present for all of it.

Connect

Remote — hosted world or free room

The hosted server speaks Streamable HTTP with OAuth 2.1 (dynamic client registration).

Claude Code:

claude mcp add --transport http living-memory https://lme.viibe.to/mcp

claude.ai / Claude Desktop: Settings → Connectors → Add custom connector → https://lme.viibe.to/mcp.

ChatGPT: Settings → enable Developer Mode, then add https://lme.viibe.to/mcp as a custom connector. Availability may depend on your ChatGPT plan.

It's 2026. MCP client support changes faster than READMEs do — ask your agent whether your client supports remote MCP today.

Free room, no signup — for trying the whole loop, or for clients without OAuth:

curl -X POST https://lme.viibe.to/ons/new
# → {"url": "https://lme.viibe.to/t/<token>/mcp", "expiresAt": "..."}

The returned URL is a private streamable-HTTP MCP endpoint (no auth header). The room stays available while it's used — any successful use keeps it alive; left inactive it is eventually forgotten, and its data is then deleted. A room differs from a world by how long it lasts, not by what it can do.

Local — stdio, open source

The npm package runs the memory surface as a local stdio server: one JSON file on your machine, can run fully offline.

claude mcp add living-memory -s user -- npx -y @nature-labs/lme-mcp

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Living Memory: common questions

Is Living Memory MCP server safe?
Yes, by our scan: it is graded A (94/100). Read the Living Memory safety report
How do I install Living Memory?
It runs remotely at lme.viibe.to. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Living Memory need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Living Memory maintained?
The last commit was 33 days ago (2026-10-02). The latest release is v0.1.2.
Is Living Memory up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Living Memory?
Servers from other publishers that do the same job: Mobilerun MCP server.
How does Living Memory compare with other MCP servers?
safety score 94/100 (higher than 96% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 604 ms (faster than 24% of 30,031 servers). Full comparison.

Alternatives to Living Memory

Same job from other publishers: the closest match first, then the best rated.

  • Mobilerun
    Let AI agents control Android and iOS devices on Mobilerun Cloud: screen, input, apps, workflows.
    A