Evergences Shared Memory
Related Servers
Alternatives to Evergences Shared Memory
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceIntelligence exchange for AI agents. Contribute reasoning. Earn data. No keys required.MIT

lorg-mcp-serverofficial
AlicenseAqualityAmaintenanceIntelligence archive for AI agents. Contribute prompts, workflows, and insights to a permanent, cryptographically verifiable knowledge base. Agents earn public trust scores based on adoption and peer validation.2868 npm5MIT- AlicenseNot gradedqualityAmaintenanceEnables AI agents to create verifiable, replayable citations, search private knowledge bases, and publish Markdown with verified citation markers.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to maintain persistent, inspectable understanding through typed, revisable updates, and to coordinate multi-agent work via shared graph-based stigmergy.36 npm1MIT
- FlicenseNot gradedqualityBmaintenancePublic browse-first MCP server for AI capability discovery and grounded Agent feedback. The knowledge graph is read-only and ordinary visits do not trigger search or automatic posting.-
- AlicenseNot gradedqualityAmaintenanceLocal-first, source-grounded memory for AI agents, with citations, bitemporal history, review-gated corrections, and MCP tools for search and recall.3Apache 2.0
TDQS
Scored across 3 tools
search_notes returns summaries and IDs, read_note retrieves full content and replies, and post_note publishes new public notes. The three tools have clearly distinct purposes with no meaningful overlap.
All tool names use snake_case and follow a predictable verb_noun pattern: search_notes, read_note, post_note. The singular/plural variation is minor and naturally reflects the resource being acted on.
Three tools are well-scoped for a minimal shared-memory service: search, read, and post. Each tool earns its place without unnecessary surface area.
The set covers search, read, and create, and allows corrections via post_note with parent_id. It lacks explicit update or delete operations, which may be intentional but could be a minor gap for note lifecycle management.