# ai.memoryrouter/memoryrouter

Persistent AI memory shared across Claude, ChatGPT, coding agents, and compatible MCP clients.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.1.0
- **Author:** ai.memoryrouter
- **License:** Unknown
- **Endpoints:** streamable-http https://mcp.memoryrouter.ai/mcp
- **Source:** https://memoryrouter.ai
- **Endpoint health:** reachable (last checked 2026-09-18T05:13:24.971Z, 4 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-18T05:13:24.971Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

10 declared. Observed from a live `tools/list` probe.
- `search_memories` — Use this when the user asks about a prior decision, preference, person, project, or other fact that may be in their connected MemoryRouter vault. Semantically s
- `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
- `store_memory` — Use this only when the user explicitly asks to remember something or confirms a proposed durable fact. Saves concise user-approved content to the OAuth-selected
- `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
- `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 
- `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
- `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
- `inspect_memory` — Use this when the user asks why the assistant believes something, or wants to see the source memories behind a reflection. Given a memory id from a search resul
- `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
- `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

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"memoryrouter\": {\n      \"type\": \"http\",\n      \"url\": \"https://mcp.memoryrouter.ai/mcp\"\n    }\n  }\n}"
```

## Blast radius

Moderate to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on someone else's infrastructure.
- Floor 32, ceiling 56 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/ai.memoryrouter%2Fmemoryrouter
- Install plan: https://forgeregistry.com/api/v1/packages/ai.memoryrouter%2Fmemoryrouter/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/ai.memoryrouter%2Fmemoryrouter
- HTML page: https://forgeregistry.com/registry/ai.memoryrouter%2Fmemoryrouter
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.