Other · Remote MCP server
Living Memory
An MCP memory server. One memory your agents share - across models, devices and apps.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
to.viibe/living-memory- Version
- 0.1.2
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-08-15
- Updated
- 2026-08-15
- Publisher
- to.viibe
- Namespace
- Namespace verified by the MCP Registry via the domain viibe.to · how
- Website
- viibe.to/living-memory/
- Repository
- github.com/v1b3x0r/living-memory-engine
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://lme.viibe.to/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @nature-labs/lme-mcp | 0.1.2 | stdio |
How to connect Living Memory
Living Memory is a remote MCP server: there is nothing to install. Its endpoint is https://lme.viibe.to/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @nature-labs/lme-mcp version 0.1.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @nature-labs/lme-mcp@0.1.2.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"living-memory": {
"command": "npx",
"args": [
"-y",
"@nature-labs/lme-mcp@0.1.2"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Livepilot317-tool agentic MCP production system for Ableton Live 12 - device atlas, sample engine, composer. | Local · stdio |
| Livestock Counterparty GuardVerify livestock buyers, dealers, market agencies, and packers against USDA P&S records. | Remote · HTTPLive check: ✓ handshake |
| Livetennisapi MCPLive tennis scores, players, rankings, odds and win-probability. ATP, WTA, Challenger, ITF, juniors. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Livewire Client Surface AuditMarks every line of a Livewire or Blade file that the visitor's browser can call, rewrite or read. | Local · stdio |
| Living Stack Agent CommerceRemote MCP for Living Stack offer discovery and buyer-authorized checkout preparation. | Remote · HTTPLive check: ✓ handshake |
| Living Stack CommunityFree seven-tool proof loop for scoped authorization, outcome receipts, and evidence-bound claims. | Local · stdio |
| LlamanotesLucky AI study buddy over your own LlamaNotes courses: chat, progress, and AI course generation. | Remote · HTTPLive check: sign-in required |
| LMGramConsent-based human matchmaking for peer advice, collaboration, and practical help. | Remote · HTTPLive check: ✓ handshake |