Mnemoverse Memory
Mnemoverse Memory is an MCP server published by mnemoverse, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does Mnemoverse Memory support the current MCP specification (2026-07-28)?
Not yet confirmed. Mnemoverse Memory is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is Mnemoverse Memory a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for Mnemoverse Memory (as of 2026-08-20).
How do I connect to Mnemoverse Memory?
Mnemoverse Memory is available via a hosted remote endpoint at https://mcp.mnemoverse.com/mcp, the package npm:@mnemoverse/mcp-memory-server, the official MCP Registry under io.github.mnemoverse/mcp-memory-server, the source repository at https://github.com/mnemoverse/mcp-memory-server. Authentication: oauth. Transports: streamable-http.
Does Mnemoverse Memory support MCP revision 2025-11-25?
Yes. Mnemoverse Memory supports MCP revision 2025-11-25 (checked 2026-08-20).
Does Mnemoverse Memory support MCP revision 2026-07-28?
No. Mnemoverse Memory was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were Mnemoverse Memory's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Hosted memory for AI agents that learns and forgets - one key across Claude, Cursor & ChatGPT.
Which MCP spec revisions does Mnemoverse Memory support?
Mnemoverse Memory has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is Mnemoverse Memory?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for Mnemoverse Memory
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Stars
- 20
- Forks
- 4
- Last pushed
- (38 days ago)
- Created
- Open issues
- 21
- Primary language
- TypeScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- None
Declared topics: ai-memory, anthropic, chatgpt, claude, cross-tool, cursor, forgetting, hosted-memory, mcp-server, modelcontextprotocol, persistent-memory, typescript — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
0.9.1- Last published
- First published
- Releases
- 25
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 2
- Unpacked size
- 277 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.mnemoverse/mcp-memory-server at version 0.8.0 - lists remote endpoint https://mcp.mnemoverse.com/mcp and repository https://github.com/mnemoverse/mcp-memory-server - accessed
- Endpoint probe of https://mcp.mnemoverse.com/mcp - authorization required (HTTP 401, Bearer error="invalid_request" error_description="Missing be); capability set not observable without credentials - accessed
- npm registry metadata for @mnemoverse/mcp-memory-server at published version 0.8.4, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed