# Memoryrouter MCP server

Source: https://glimind.com/server/mcp-registry%2Fai.memoryrouter%2Fmemoryrouter
Registry id: `mcp-registry/ai.memoryrouter/memoryrouter`
Status: live (checked 2026-11-22T12:28:51.422Z)

## Verdict

Memoryrouter MCP server answered 99.95% of Glimind's liveness checks over 30 days, better than 32% of MCP servers, with 221 ms median handshake and 5 outages in 90 days. Its agent-readiness grade is A (97/100) across 14 tools, costing an agent about 3,971 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.95% | 32% of MCP servers |
| Median handshake latency | 221 ms | 55% of MCP servers |
| p95 handshake latency | 606 ms | — |
| Checks in 30 days | 6,931 | — |
| Outages, 90 days | 5 | — |
| Median recovery | 2 min | — |
| Agent-readiness score | 97/100 (A) | 88% of MCP servers |
| Tools | 14 | — |
| Tool-list size for an agent | ~3,971 tokens | 33% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "memoryrouter-mcp-server": {
      "type": "http",
      "url": "https://mcp.memoryrouter.ai/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http memoryrouter-mcp-server https://mcp.memoryrouter.ai/mcp
```

## Tools (14)

- `commit_reflections`: Use this to complete a consolidation started with consolidate_memories. Submits the reflection entries you wrote for the checked-out batch. Each entry is standa
- `consolidate_memories`: Use this when the user asks to consolidate, reflect on, or organize their memories, or when memory_status or a search result reports that consolidation is avail
- `create_memory_share`: Use this when the user asks to share memories with another person or another MemoryRouter account, for example 'make a share link for everything about project X
- `date_search_memories`: Use this to retrieve memories from a specific time window, for questions like 'what happened last week' or 'most important things this month or lately'. Tier gu
- `delete_memories`: Use this only when the user explicitly asks to delete specific memories and confirms after seeing what will be deleted. Permanently deletes the identified memor
- `forget_all_memories`: Use this only after the user explicitly requests a full-vault deletion, receives a permanent whole-vault warning, and provides the exact confirmation phrase in 
- `import_memory_share`: Use this when the user pastes a MemoryRouter share link (app.memoryrouter.ai/transfer/...) with its password and asks to import it. The first call (no confirmat
- `inspect_memory`: Use this when exact details or provenance matter: when the user asks why the assistant believes something, or wants to see the source memories behind a reflecti
- `list_memory_shares`: Use this when the user asks which share links exist for the connected vault, or needs a share id to revoke. Lists each link with its status, memory count, uses 
- `memory_status`: Use this when the user asks whether MemoryRouter is connected, which opaque vault binding is active, or how many memories/tokens the connected vault contains. D
- `revoke_memory_share`: Use this when the user asks to revoke, cancel or turn off a share link. Stops all future imports from that link. Copies that were already imported stay in the o
- `search`: Use this legacy compatibility alias when a client explicitly requests a tool named search. It searches the OAuth-selected MemoryRouter vault without modifying i
- `search_memories`: Use this before responding to each new user message, to retrieve context relevant to the message and ongoing conversation, even when the user does not explicitl
- `store_memory`: Use this after each user message that contains anything worth knowing later, even if the user does not say 'remember this'. Default to saving: a missed memory c

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
