# Fluid Recall (remote · fluidrecall.com)

Agent-native spaced-recall system of record. Deterministic dueAt via remote MCP for Muse/any agent.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `fluidrecall.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-fluidrecall-mcp/fluidrecall.md), [page](https://verifymcp.io/servers/com-fluidrecall-mcp/fluidrecall)

## Channel facts

- Endpoint: `https://fluidrecall.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 5085 tokens (~130/item across 39 items; 39 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 73/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 20% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 40 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Fluid Recall MCP server?

Fluid Recall is a hosted endpoint at https://fluidrecall.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-fluidrecall-mcp 'https://fluidrecall.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-fluidrecall-mcp": {
      "url": "https://fluidrecall.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-fluidrecall-mcp": {
      "type": "http",
      "url": "https://fluidrecall.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-fluidrecall-mcp]
url = "https://fluidrecall.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-fluidrecall-mcp": {
      "type": "remote",
      "url": "https://fluidrecall.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-fluidrecall-mcp --url 'https://fluidrecall.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-fluidrecall-mcp:
    url: "https://fluidrecall.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-fluidrecall-mcp": {
      "Transport": "http",
      "Url": "https://fluidrecall.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-fluidrecall-mcp -t streamable-http -u 'https://fluidrecall.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-fluidrecall-mcp": {
      "type": "http",
      "url": "https://fluidrecall.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-29 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-28 (score 64)

First indexed and scored.

## MCP tools (39)

### `createAccount` (~55 tokens)

Write. No bearer. Mint an anonymous account and a personal API token. Save the token for later Authorization: Bearer calls. The token is the tenant. Do not send a userId.

Input parameters:

- `label` (string|null)

### `bootstrapAccount` (~27 tokens)

Write. Same mint as createAccount. No bearer.

Input parameters:

- `label` (string|null)

### `startSession` (~326 tokens)

Write when no bearer (mints a token), read when a bearer is present. Returns the account (when minted), the due queue, and first. Prompts only. Includes deckNote and cardNote (null when unset). Coaching notes are instructions for how an agent should quiz and coach. They are not the answer, not graded content, and not the quiz prompt. A deck note applies to every card in that deck. A card note is optional and additive with the deck note. Retrieve responses (listDue, upcoming-new, inventory, getCard, reveal, and agent session start/next/grade) include deckNote and cardNote so one call carries coaching context. Scripture / dictation: The learner needs every word remembered correctly, but often answers via dictation where punctuation gets messy. They set a deck note instructing the agent to check every word exactly, but not fail on punctuation differences, and to include that reason when coaching. This is only an example — notes can be any coaching preference for how agents should quiz/coach for that deck (or a specific card). A wrong bearer is 401 and does not create an account. Do not send newCardMode extra on the first call.

Input parameters:

- `asOf` (string): Queue instant. Omit to use now.
- `deckId` (string): Optional deck filter.
- `extraNew` (integer): Required when newCardMode is extra.
- `label` (string|null)
- `limit` (integer): Page size, not the daily new-card cap.
- `newCardMode` (string)

### `nextDue` (~274 tokens)

Read. Due queue and first prompt. Requires a bearer. Prompts only. Includes deckNote and cardNote (null when unset). Coaching notes are instructions for how an agent should quiz and coach. They are not the answer, not graded content, and not the quiz prompt. A deck note applies to every card in that deck. A card note is optional and additive with the deck note. Retrieve responses (listDue, upcoming-new, inventory, getCard, reveal, and agent session start/next/grade) include deckNote and cardNote so one call carries coaching context. Scripture / dictation: The learner needs every word remembered correctly, but often answers via dictation where punctuation gets messy. They set a deck note instructing the agent to check every word exactly, but not fail on punctuation differences, and to include that reason when coaching. This is only an example — notes can be any coaching preference for how agents should quiz/coach for that deck (or a specific card).

Input parameters:

- `asOf` (string): Queue instant. Omit to use now.
- `deckId` (string): Optional deck filter.
- `extraNew` (integer): Required when newCardMode is extra.
- `limit` (integer): Page size, not the daily new-card cap.
- `newCardMode` (string)

### `gradeAndNext` (~339 tokens)

Write. recordReview, then the next due prompt. Requires cardId, rating, reviewedAt optional, and a new idempotencyKey. Schedule from dueAt. Prompts only. Includes deckNote and cardNote (null when unset). Coaching notes are instructions for how an agent should quiz and coach. They are not the answer, not graded content, and not the quiz prompt. A deck note applies to every card in that deck. A card note is optional and additive with the deck note. Retrieve responses (listDue, upcoming-new, inventory, getCard, reveal, and agent session start/next/grade) include deckNote and cardNote so one call carries coaching context. Scripture / dictation: The learner needs every word remembered correctly, but often answers via dictation where punctuation gets messy. They set a deck note instructing the agent to check every word exactly, but not fail on punctuation differences, and to include that reason when coaching. This is only an example — notes can be any coaching preference for how agents should quiz/coach for that deck (or a specific card).

Input parameters:

- `asOf` (string): Queue instant. Omit to use now.
- `cardId` (string, required)
- `deckId` (string): Optional deck filter.
- `extraNew` (integer): Required when newCardMode is extra.
- `idempotencyKey` (string, required)
- `limit` (integer): Page size, not the daily new-card cap.
- `newCardMode` (string)
- `rating` (string, required)
- `reviewedAt` (string): UTC ISO-8601 timestamp ending in Z

### `getStudySettings` (~39 tokens)

Read. Account fallback newCardsPerDay, timezone, and dayBoundaryHour. The fallback applies only to a deck whose own field is still null.

### `updateStudySettings` (~64 tokens)

Write. Change the account fallback, timezone, or day boundary. Decks that already store an integer keep it. Send at least one field.

Input parameters:

- `dayBoundaryHour` (integer)
- `newCardsPerDay` (integer)
- `timezone` (string)

### `createDeck` (~98 tokens)

Write. name and newCardsPerDay are required. Choose that integer with the person; there is no default of 20. Optional description and deckNote. Setting a note does not move dueAt.

Input parameters:

- `deckNote` (string|null): Coaching instructions for every card in this deck. Null clears. Not the answer.
- `description` (string|null)
- `name` (string, required)
- `newCardsPerDay` (integer, required)

### `updateDeck` (~89 tokens)

Write. Rename, rewrite description, set or clear deckNote, and/or set newCardsPerDay. Send at least one. Null deckNote clears it. Does not move dueAt.

Input parameters:

- `deckId` (string, required)
- `deckNote` (string|null)
- `description` (string|null)
- `name` (string)
- `newCardsPerDay` (integer|null)

### `setDeckNote` (~226 tokens)

Write. Set or clear a deck coaching note. deckNote null clears it. Same write as updateDeck. Does not move dueAt. Coaching notes are instructions for how an agent should quiz and coach. They are not the answer, not graded content, and not the quiz prompt. A deck note applies to every card in that deck. A card note is optional and additive with the deck note. Retrieve responses (listDue, upcoming-new, inventory, getCard, reveal, and agent session start/next/grade) include deckNote and cardNote so one call carries coaching context. Scripture / dictation: The learner needs every word remembered correctly, but often answers via dictation where punctuation gets messy. They set a deck note instructing the agent to check every word exactly, but not fail on punctuation differences, and to include that reason when coaching. This is only an example — notes can be any coaching preference for how agents should quiz/coach for that deck (or a specific card).

Input parameters:

- `deckId` (string, required)
- `deckNote` (string|null, required)

### `listDecks` (~38 tokens)

Read. No card bodies. Archived decks omitted unless includeArchived is true. Each deck includes deckNote.

Input parameters:

- `includeArchived` (boolean)

### `archiveDeck` (~35 tokens)

Write. Soft-archive. Cards and schedules stay. A second call returns alreadyArchived true.

Input parameters:

- `deckId` (string, required)

### `unarchiveDeck` (~36 tokens)

Write. Clear archivedAt. Schedule fields stay. An already-active deck returns alreadyActive true.

Input parameters:

- `deckId` (string, required)

### `addCard` (~70 tokens)

Write. Add one prompt/answer pair. Optional cardNote. Eligible immediately. listDue still applies newCardsPerDay. The response is prompts only.

Input parameters:

- `answer` (string, required)
- `cardNote` (string|null)
- `deckId` (string, required)
- `prompt` (string, required)

### `addCards` (~61 tokens)

Write. Add 1 to 100 prompt/answer pairs to one owned deck. All or nothing. Prompts only. After this, re-run previewDeadlinePlan with that deckId.

Input parameters:

- `cards` (array, required)
- `deckId` (string, required)

### `updateCard` (~72 tokens)

Write. Correct prompt, answer, and/or cardNote. Send at least one. cardNote null clears it. Schedule stays. Response does not include the answer.

Input parameters:

- `answer` (string)
- `cardId` (string, required)
- `cardNote` (string|null)
- `prompt` (string)

### `setCardNote` (~233 tokens)

Write. Set or clear a card coaching note. cardNote null clears it. Additive with the deck note. Same write as updateCard. Does not include the answer. Coaching notes are instructions for how an agent should quiz and coach. They are not the answer, not graded content, and not the quiz prompt. A deck note applies to every card in that deck. A card note is optional and additive with the deck note. Retrieve responses (listDue, upcoming-new, inventory, getCard, reveal, and agent session start/next/grade) include deckNote and cardNote so one call carries coaching context. Scripture / dictation: The learner needs every word remembered correctly, but often answers via dictation where punctuation gets messy. They set a deck note instructing the agent to check every word exactly, but not fail on punctuation differences, and to include that reason when coaching. This is only an example — notes can be any coaching preference for how agents should quiz/coach for that deck (or a specific card).

Input parameters:

- `cardId` (string, required)
- `cardNote` (string|null, required)

### `retireCard` (~34 tokens)

Write. Remove a card from future drills. A second call returns alreadyRetired true.

Input parameters:

- `cardId` (string, required)

### `unretireCard` (~36 tokens)

Write. Clear retiredAt. Schedule stays. An already-active card returns alreadyActive true.

Input parameters:

- `cardId` (string, required)

### `moveCard` (~53 tokens)

Write. Move an active card into another owned deck. Schedule stays. A card already there returns alreadyThere true. Does not include the answer.

Input parameters:

- `cardId` (string, required)
- `deckId` (string, required)

### `listDue` (~292 tokens)

Read. Prompts only. answerIncluded is false. Ordered learning, then review, then new. The new queue is capped by each deck's newCardsPerDay. Includes deckNote and cardNote (null when unset). Coaching notes are instructions for how an agent should quiz and coach. They are not the answer, not graded content, and not the quiz prompt. A deck note applies to every card in that deck. A card note is optional and additive with the deck note. Retrieve responses (listDue, upcoming-new, inventory, getCard, reveal, and agent session start/next/grade) include deckNote and cardNote so one call carries coaching context. Scripture / dictation: The learner needs every word remembered correctly, but often answers via dictation where punctuation gets messy. They set a deck note instructing the agent to check every word exactly, but not fail on punctuation differences, and to include that reason when coaching. This is only an example — notes can be any coaching preference for how agents should quiz/coach for that deck (or a specific card).

Input parameters:

- `asOf` (string): Queue instant. Omit to use now.
- `deckId` (string): Optional deck filter.
- `extraNew` (integer): Required when newCardMode is extra.
- `limit` (integer): Page size, not the daily new-card cap.
- `newCardMode` (string)

### `listUpcomingNew` (~239 tokens)

Read. New cards the daily cap is holding back. Prompts only. Includes deckNote and cardNote (null when unset). Coaching notes are instructions for how an agent should quiz and coach. They are not the answer, not graded content, and not the quiz prompt. A deck note applies to every card in that deck. A card note is optional and additive with the deck note. Retrieve responses (listDue, upcoming-new, inventory, getCard, reveal, and agent session start/next/grade) include deckNote and cardNote so one call carries coaching context. Scripture / dictation: The learner needs every word remembered correctly, but often answers via dictation where punctuation gets messy. They set a deck note instructing the agent to check every word exactly, but not fail on punctuation differences, and to include that reason when coaching. This is only an example — notes can be any coaching preference for how agents should quiz/coach for that deck (or a specific card).

Input parameters:

- `asOf` (string): UTC ISO-8601 timestamp ending in Z
- `deckId` (string)
- `limit` (integer)

### `listDeckCards` (~258 tokens)

Read. Prompt-only inventory of one owned deck, including cards that are not due. Order is dueAt, then createdAt, then cardId — not the drill order. Includes deckNote and cardNote (null when unset). Coaching notes are instructions for how an agent should quiz and coach. They are not the answer, not graded content, and not the quiz prompt. A deck note applies to every card in that deck. A card note is optional and additive with the deck note. Retrieve responses (listDue, upcoming-new, inventory, getCard, reveal, and agent session start/next/grade) include deckNote and cardNote so one call carries coaching context. Scripture / dictation: The learner needs every word remembered correctly, but often answers via dictation where punctuation gets messy. They set a deck note instructing the agent to check every word exactly, but not fail on punctuation differences, and to include that reason when coaching. This is only an example — notes can be any coaching preference for how agents should quiz/coach for that deck (or a specific card).

Input parameters:

- `cursor` (string)
- `deckId` (string, required)
- `includeRetired` (boolean)
- `limit` (integer)

### `inventoryDeck` (~246 tokens)

Read. Same as listDeckCards. Use this when you need a cardId that is not in the due list. Includes deckNote and cardNote (null when unset). Coaching notes are instructions for how an agent should quiz and coach. They are not the answer, not graded content, and not the quiz prompt. A deck note applies to every card in that deck. A card note is optional and additive with the deck note. Retrieve responses (listDue, upcoming-new, inventory, getCard, reveal, and agent session start/next/grade) include deckNote and cardNote so one call carries coaching context. Scripture / dictation: The learner needs every word remembered correctly, but often answers via dictation where punctuation gets messy. They set a deck note instructing the agent to check every word exactly, but not fail on punctuation differences, and to include that reason when coaching. This is only an example — notes can be any coaching preference for how agents should quiz/coach for that deck (or a specific card).

Input parameters:

- `cursor` (string)
- `deckId` (string, required)
- `includeRetired` (boolean)
- `limit` (integer)

### `getCard` (~218 tokens)

Read. One card's prompt and schedule. No answer. A retired card is 404. Includes deckNote and cardNote (null when unset). Coaching notes are instructions for how an agent should quiz and coach. They are not the answer, not graded content, and not the quiz prompt. A deck note applies to every card in that deck. A card note is optional and additive with the deck note. Retrieve responses (listDue, upcoming-new, inventory, getCard, reveal, and agent session start/next/grade) include deckNote and cardNote so one call carries coaching context. Scripture / dictation: The learner needs every word remembered correctly, but often answers via dictation where punctuation gets messy. They set a deck note instructing the agent to check every word exactly, but not fail on punctuation differences, and to include that reason when coaching. This is only an example — notes can be any coaching preference for how agents should quiz/coach for that deck (or a specific card).

Input parameters:

- `cardId` (string, required)

### `revealCard` (~221 tokens)

Important read. One answer, after the person has tried to recall. Do not fold this into listDue. Includes deckNote and cardNote (null when unset). Coaching notes are instructions for how an agent should quiz and coach. They are not the answer, not graded content, and not the quiz prompt. A deck note applies to every card in that deck. A card note is optional and additive with the deck note. Retrieve responses (listDue, upcoming-new, inventory, getCard, reveal, and agent session start/next/grade) include deckNote and cardNote so one call carries coaching context. Scripture / dictation: The learner needs every word remembered correctly, but often answers via dictation where punctuation gets messy. They set a deck note instructing the agent to check every word exactly, but not fail on punctuation differences, and to include that reason when coaching. This is only an example — notes can be any coaching preference for how agents should quiz/coach for that deck (or a specific card).

Input parameters:

- `cardId` (string, required)

### `recordReview` (~92 tokens)

Write. Rating again | hard | good | easy plus reviewedAt and a new idempotencyKey. The scheduler returns dueAt. Do not invent an interval. Same key and body returns the original result.

Input parameters:

- `cardId` (string, required)
- `idempotencyKey` (string, required)
- `rating` (string, required)
- `reviewedAt` (string): UTC ISO-8601 timestamp ending in Z

### `undoReview` (~66 tokens)

Write. Undo the latest active grade, or reviewId when it is that latest one. Restores dueAt. A second undo of the same review returns alreadyUndone true. Does not include the answer.

Input parameters:

- `cardId` (string, required)
- `reviewId` (string)

### `previewDeadlinePlan` (~192 tokens)

Read. Recommend newCardsPerDay from a deadline: ceil(remaining new cards / study days). Does not write. Send remainingNewCards, totalCards, or deckId. There is no silent default of 20.

Input parameters:

- `alreadyLearned` (integer)
- `asOf` (string): UTC ISO-8601 timestamp ending in Z
- `bufferStudyDays` (integer)
- `currentNewCardsPerDay` (integer|null)
- `dayBoundaryHour` (integer)
- `deadline` (string, required): YYYY-MM-DD or a UTC ISO-8601 timestamp ending in Z.
- `deckId` (string)
- `remainingNewCards` (integer)
- `skipWeekends` (boolean)
- `studyDaysPerWeek` (integer)
- `timezone` (string): IANA timezone such as UTC or America/Denver.
- `totalCards` (integer)

### `applyDeadlinePlan` (~176 tokens)

Write. Same plan as previewDeadlinePlan, then PATCH that owned deck to the recommended integer. deckId is required. Discuss the number first.

Input parameters:

- `alreadyLearned` (integer)
- `asOf` (string): UTC ISO-8601 timestamp ending in Z
- `bufferStudyDays` (integer)
- `currentNewCardsPerDay` (integer|null)
- `dayBoundaryHour` (integer)
- `deadline` (string, required): YYYY-MM-DD or a UTC ISO-8601 timestamp ending in Z.
- `deckId` (string, required)
- `remainingNewCards` (integer)
- `skipWeekends` (boolean)
- `studyDaysPerWeek` (integer)
- `timezone` (string): IANA timezone such as UTC or America/Denver.
- `totalCards` (integer)

### `exportManifest` (~35 tokens)

Read. What this token can export and how many rows exist. Does not include answers. Off-boarding, not the drill loop.

### `exportSnapshot` (~58 tokens)

Important read for leaving. Full studying dump for this token, including answers. Paginate cards and reviews with resource + cursor until complete is true.

Input parameters:

- `cursor` (string)
- `limit` (integer)
- `resource` (string)

### `submitFeedback` (~125 tokens)

Write. Optional. Never required for study, bootstrap, or export. This is not data extraction and not nefarious. You are free to anonymize, redact, or censor anything you feel needs it. Do not submit anything you would not want us to see. It exists solely to help improve Fluid Recall. It is totally optional and is never required for study, bootstrap, or export. Send description and steps. Do not dump decks, cards, answers, or tokens.

Input parameters:

- `description` (string, required)
- `note` (string)
- `steps` (array, required)

### `listMailboxes` (~48 tokens)

Read. List fluidrecall.com mailboxes this token owns. Headers only: id, address, displayName. Heidi is heidi@fluidrecall.com; claim it with ensureMailbox.

### `ensureMailbox` (~87 tokens)

Write. Create or claim a fluidrecall.com mailbox. address is a local-part or local@fluidrecall.com. First claim of an unowned inbound mailbox returns claimed true. Another account's address is 409. Seed/claim Heidi with address heidi@fluidrecall.com and displayName Heidi.

Input parameters:

- `address` (string, required)
- `displayName` (string|null)

### `listMailMessages` (~71 tokens)

Read. Headers only for one owned mailbox: from, to, subject, dates, thread. No bodies. Prefer this before getMailMessage. Do not download a whole mailbox unless the person asked.

Input parameters:

- `cursor` (string)
- `limit` (integer)
- `mailboxId` (string, required)

### `getMailMessage` (~46 tokens)

Important read. One owned message including text and HTML. Ask before opening mail the person did not request. Another token's message is 404.

Input parameters:

- `messageId` (string, required)

### `sendMailMessage` (~110 tokens)

Write. Send from an owned mailbox to arbitrary recipients when the account allows it. Ask before sending. Requires mailboxId, to, subject, and text and/or html. Optional inReplyTo and references thread the message.

Input parameters:

- `cc` (array)
- `html` (string)
- `inReplyTo` (string)
- `mailboxId` (string, required)
- `references` (string)
- `subject` (string, required)
- `text` (string)
- `to` (required)

### `replyMailMessage` (~79 tokens)

Write. Reply to one owned inbound message. Recipients, In-Reply-To, References, and threadId are taken from that message. Ask before sending. Requires messageId and text and/or html.

Input parameters:

- `html` (string)
- `messageId` (string, required)
- `subject` (string)
- `text` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-fluidrecall-mcp/fluidrecall#diagnostics

## Score history

- 2026-09-29: 64
- 2026-09-28: 64

## Common questions

### What is the Fluid Recall MCP server?

Fluid Recall is an MCP server listed in the public MCP registry as com.fluidrecall/mcp. Agent-native spaced-recall system of record. Deterministic dueAt via remote MCP for Muse/any agent. This page covers its hosted endpoint (https://fluidrecall.com/mcp).

### Is the Fluid Recall MCP server safe to use?

Fluid Recall scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Fluid Recall MCP server expose?

Fluid Recall exposes 39 tools: createAccount, bootstrapAccount, startSession, nextDue, gradeAndNext, and 34 more. Their descriptions and schemas cost roughly 4,864 tokens of context every time the server is loaded.

### Does the Fluid Recall MCP server require authentication?

No. We connected to Fluid Recall without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Fluid Recall MCP server still maintained?

Fluid Recall is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://fluidrecall.com/mcp
- Website: https://fluidrecall.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-fluidrecall-mcp/fluidrecall.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-fluidrecall-mcp/fluidrecall.json
- HTML version of this page: https://verifymcp.io/servers/com-fluidrecall-mcp/fluidrecall
