MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

Mnemoverse Memory

Spec Support Unverified Publisher unverified Confidence: Good (0.85)

Mnemoverse Memory is an MCP server published by mnemoverse; its MCP spec-revision support has not been verified yet. Last verified 2026-08-07.

Does Mnemoverse Memory support the current MCP specification (2026-07-28)?

Undetermined. We have not verified which MCP specification revision Mnemoverse Memory supports (as of 2026-08-07).

Is Mnemoverse Memory a first-party (official) MCP server?

Undetermined. We have not verified the publisher relationship for Mnemoverse Memory (as of 2026-08-07).

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.

When were Mnemoverse Memory's facts last verified?

2026-08-07. 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.

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.

How was this verified, and what are the sources?

Verified · method: registry-record · confidence 0.85 (Good).

  1. 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
  2. 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