com.runmemento/memento
com.runmemento/memento
Is the com.runmemento/memento MCP server down? No. It is up and needs env, probed 2026-10-26.
Local-first, LLM-agnostic memory layer for AI assistants.
needs env probed 2026-11-15 · unchanged since 2026-10-26
MCP error -32000: Connection closed
{"ok":false,"error":{"code":"STORAGE_ERROR","message":"failed to open database at 'mcpcost-placeholder': Could not locate th- Run it
- npx -y @psraghuveer/memento@0.9.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/veerps57/memento.git
- Website
- https://runmemento.com
- Registry
- active, updated 2026-05-17 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Unified B2B ATS Jobs Scraper & MCP (Greenhouse, Workday, Lever, Ashby) | RevClamp TalentPulse com.revclamp/unified-ats-jobs-mcp · crashed on start
- com.rolnia/mcp · alive
- Rowsend com.rowsend/rowsend · install failed
- com.ruddia/being-mcp-server · alive
- Scannd com.scannd/scannd · alive
- com.scopeblind/passport · needs env
- com.scopeblind/protect-mcp · alive
- com.scopeblind/verify-mcp · alive
Servers that mention memento.
- Memento io.github.mementoagi/memento · needs auth
- io.github.myrakrusemark/memento-protocol · alive
- Memento io.github.jee1/memento-mcp-server · crashed on start
- io.github.annibale-x/mcp-memento · crashed on start
- memento Team claims io.gitlab.memento-team-hq/memento-team · alive
- Memento io.github.scrypster/memento · not found
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-26 06:58 | needs env | ||||
| 2026-10-19 06:50 | crashed on start |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server exits because an environment variable is missing. The probe starts the package without secrets. A server that starts without secrets and asks for them on the first tool call is measured.