Home / MCP registry index / com.fluidrecall/mcp
Fluid Recall
com.fluidrecall/mcp in the official MCP registry.
Endpoint https://fluidrecall.com/mcp.
The registry describes it as: Agent-native spaced-recall system of record. Deterministic dueAt via remote MCP for Muse/any agent.
We read its 34 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
createAccount bootstrapAccount startSession nextDue gradeAndNext getStudySettings get_profile updateStudySettings createDeck updateDeck setDeckNote listDecks archiveDeck unarchiveDeck addCard addCards updateCard setCardNote retireCard unretireCard moveCard listDue listUpcomingNew listDeckCards inventoryDeck getCard revealCard recordReview undoReview previewDeadlinePlan applyDeadlinePlan exportManifest exportSnapshot submitFeedback
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-fluidrecall-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.