Fluid Recall
com.fluidrecallv1.0.0Updated Sep 28, 2026
Agent-native spaced-recall system of record. Deterministic dueAt via remote MCP for Muse/any agent.
Overview
AI-generated overview
Gives an assistant a hosted spaced-recall record it can read and schedule, with deterministic due dates.
- What it does
- Fluid Recall is described as an agent-native spaced-recall system of record, exposed as a remote MCP endpoint. According to the registry description, it provides deterministic dueAt scheduling so an agent can decide when a recalled item is due. It is presented as usable by Muse or any agent. No tool list is published in the manifest.
- When to use it
- Relevant if you want an assistant to manage repeated review of items over time and rely on consistent due dates rather than ad hoc scheduling. Probably not useful for one-off lookups, since the described purpose is tracking recall state across sessions.
- Requirements
- A remote streamable HTTP MCP endpoint at fluidrecall.com; the assistant must be able to reach it over the network. The manifest declares no packages, authentication, environment variables, or headers.
Before you install
The input declares no authentication, API keys, headers, or environment variables, and no tool list is published, so what the server reads or writes cannot be verified from this listing. Recall records would be held by a third-party remote service; review its own terms before sending anything sensitive.
Installation
In SourceWeft
- Open Fluid Recall in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"mcp": {
"type": "http",
"url": "https://fluidrecall.com/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestSep 28, 2026
