Gnosem
dev.gnosem/gnosem
Cross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client.
Description as published in the official MCP registry.
Answers the MCP handshake and lists its tools. Checked 2026-10-04.
What we measured
| Endpoint | https://gnosem.dev/mcp | registry |
|---|---|---|
| Handshake | Answers the MCP handshake and lists its tools (570 ms) | our check, 2026-10-04 |
| Protocol version | 2025-06-18 | our check, 2026-10-04 |
| Tools (6) | memory_write, memory_search, memory_list, memory_forget, memory_supersede, memory_write_bulk | tools/list, 2026-10-04 |
| GitHub stars | 0 | github.com/gnosem/gnosem |
| Last push | 2026-08-26 | GitHub API |
| Licence | MIT | GitHub API |
| Registry version | 1.0.0 · active · updated 2026-07-30 | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows a real call went through, not just an opinion. How to file one.
Connect
claude mcp add --transport http gnosem https://gnosem.dev/mcpCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Badge for your README
Shows the result of our latest check and links back to this page.
[](https://openforallofus.com/tools/dev.gnosem/gnosem)Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name dev.gnosem/gnosem.