Particles
OfficialRelated Servers
Alternatives to Particles
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to record, recall, correct, and forget evidence-backed factual claims with temporal history, while explaining whether remembered information is current, historical, or contested.5Apache 2.0
- AlicenseNot gradedqualityBmaintenanceBelief-tracking memory for AI agents. Remember, recall, and ask why: every memory carries evidence, contradictions are surfaced, and retracted facts take their conclusions with them. Zero dependencies, local, MIT.MIT
- AlicenseNot gradedqualityBmaintenanceLocal-first, source-grounded memory for AI agents, with citations, bitemporal history, review-gated corrections, and MCP tools for search and recall.4Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to maintain auditable, local-first long-term memory in a single SQLite file, preserving source evidence and retiring dependent memories when sources are corrected so Claude Code, Cursor, and Codex start from current recorded evidence.158 npm159MIT
- AlicenseNot gradedqualityBmaintenanceSelf-hosted long-term memory for AI agents on your own Postgres. Facts are dated, versioned and superseded rather than silently overwritten, every recall ships with an inspectable trace, and agents can correct wrong memories from inside the conversation.2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceGives AI agents governed, provenance-tagged memory where facts are invalidated rather than deleted and every recall result carries validity dates, confidence, and replacement links. Stores memory in a local SQLite file with tools for remembering, recalling, invalidating, and pinning facts, plus policy enforcement and an audit trail.103 npm3Apache 2.0
TDQS
Scored across 16 tools
Most tools target distinct resources and actions: particles_list vs particle_show vs particle_search use different lookup axes, subjects_* split list/search/show, and events_* split list/show. The main overlap is query, a large multi-mode tool that also lists and aggregates claims, with particles_list explicitly positioned as its lightweight alternative; links_suggest and corpus_links_suggest are similarly named but clearly separated by description.
The dominant pattern is noun_verb (particles_list, particle_show, subjects_list, event_show, graph_view), but list_corpus_entries and list_taxonomies invert to verb_noun, while query and lint are bare verbs and quality_report is noun_noun. The set is still readable, but it does not follow a single consistent convention.
Sixteen tools for a read-only epistemic store spanning particles, subjects, corpus, taxonomies, events, graph rendering, diagnostics, and suggestions is reasonable, and each appears to cover a distinct surface. It sits just above the typical 3–15 range, but not heavily enough to feel mismatched.
Core read/query workflows are covered: list/search/show particles, subjects, events, corpus entries, taxonomies, plus query, graph, lint, quality, and suggestion tools. Minor gaps remain, such as no corpus_entry_show for per-entry provenance details, and mutations are absent by design because the MCP surface is read-only.