No user-submitted related servers found.
Scored across 3 tools
The three tools split cleanly by intent: search finds notes by query, get-note fetches one note's full body by path, and recent answers a temporal 'what was I doing' question from session records. The only mild overlap is that search and get-note both surface note content, but the descriptions explicitly chain them (get-note takes a path 'as returned by librarian-search').
All three share a 'librarian-' namespace prefix with kebab-case suffixes, which reads as a deliberate, predictable family. The minor deviation is that 'recent' is an adjective rather than an action verb like 'get' or 'search', so the verb_noun pattern isn't fully uniform.
Three tools is on the thin side for a knowledge-vault server, covering only retrieval. Each tool earns its place and nothing is redundant, but the surface is narrow enough that agents will frequently hit the edge of it.
The read path is coherent (search -> get-note, plus recent for recall), but there is no write/capture, update, delete, or note-listing operation anywhere in the set. If this server is meant to be the user's memory, the inability to record anything new is a notable gap; if it is deliberately read-only, the gap is smaller but still limits lifecycle coverage.