Remnant Read
OfficialRelated Servers
Alternatives to Remnant Read
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to store, search, and resolve shared memories with full provenance, conflict detection, and an audit trail across MCP-compatible clients.-

AIノアカリ☆ MCPofficial
FlicenseNot gradedqualityBmaintenanceRemote MCP server providing free tools for value-bearing responses and trust receipts, plus optional consent-based commerce, enabling agents and humans to connect to a coordinated AI operator.-- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to discover and create agents, durably submit messages with verifiable replies, and search source-linked local memory. Exposes eight authenticated tools with owner-approved OAuth, transcript-backed verification, and explicit control over history import and embedding.MIT
- AlicenseNot gradedqualityBmaintenanceA self-hosted memory ledger for AI agents. Enables agents to store, search, and share persistent memories over MCP, with a web UI and REST API.32 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables autonomous multi-agent workflows to capture, preserve, and retrieve immutable transcripts and atomic memory cards through a local MCP server, providing tools for forensic search, topic mapping, and structured fact access without losing context fidelity.1MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that adds a trust layer to AI agent memory, enforcing independent review and tamper-evident audit chains for any memory store. It provides tools to search, get, propose, and promote memories under governance rules.MIT
TDQS
Scored across 7 tools
Tools form clear pairs (search_memories→inspect_memory, find_agents→inspect_agent) and describe a genuine get→verify flow, with descriptions explicitly stating when to prefer which tool. The one soft spot is the agent-evidence cluster (inspect_agent vs get_trust_passport vs verify_trust_passport), which overlap on reported evidence and rely on prose guidance rather than sharp boundaries.
Uniform snake_case verb_noun pattern throughout (try_remnant, search_memories, inspect_memory, find_agents, inspect_agent, get_trust_passport, verify_trust_passport). Singular/plural shifts (search_memories vs inspect_memory) follow a deliberate one-vs-one result convention rather than inconsistency.
Seven tools sit squarely in the well-scoped range, with each earning its place in the read-only workflow (discovery, memory search/inspect, agent find/inspect, passport get/verify). No duplication or filler.
The read-only domain is fully covered: onboarding/discovery, memory search plus detail inspection, agent discovery plus profile inspection, and passport retrieval plus signature verification. Lifecycle has no obvious dead ends, and write operations are intentionally out of scope.