Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MemoryRouter

REMOTE · MCP.MEMORYROUTER.AI · SCANNED AUG 13

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

78 Trust /100
Trust breakdown (6 categories)

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. How we score →

Endpoint Security81
Transport & Reachability100
Schema Quality & AI Usability88
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 668 tokens (~95/item across 7 items; 5 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.memoryrouter.ai

# add to Claude Code
claude mcp add --transport http ai-memoryrouter-memoryrouter https://mcp.memoryrouter.ai/mcp
# ~/.codex/config.toml
[mcp_servers.ai-memoryrouter-memoryrouter]
url = "https://mcp.memoryrouter.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-memoryrouter-memoryrouter": {
      "type": "remote",
      "url": "https://mcp.memoryrouter.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-memoryrouter-memoryrouter --url https://mcp.memoryrouter.ai/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-memoryrouter-memoryrouter:
    url: "https://mcp.memoryrouter.ai/mcp"
// mcp.json
{
  "mcpServers": {
    "ai-memoryrouter-memoryrouter": {
      "type": "http",
      "url": "https://mcp.memoryrouter.ai/mcp"
    }
  }
}

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

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 13 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 10 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Aug 26 0
    • Stability: unverified → 0.03 functional
  • 8 Aug 26 74

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 13 Aug 2026 · Probed https://mcp.memoryrouter.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=memoryrouter.ai CN=WE1,O=Google Trust Services,C=US 11 Aug 2026 9 Nov 2026 ECDSA 256 ECDSA-SHA256 a97445c1ea8722a9131578be51479f5e
SANs: memoryrouter.ai, mcp.memoryrouter.ai, *.mcp.memoryrouter.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of mcp.memoryrouter.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
memoryrouter.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer error="invalid_token", error_description="Authentication required. Connect your MemoryRouter account.", resource_metadata="https://mcp.memoryrouter.ai/.well-known/oauth-protected-resource/mcp", scope="memories:read"

Bearer error="invalid_token", error_description="Authentication required. Connect your MemoryRouter account.", resource_metadata="https://mcp.memoryrouter.ai/.well-known/oauth-protected-resource/mcp", scope="memories:read"

Protected resource metadata

Document https://mcp.memoryrouter.ai/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://mcp.memoryrouter.ai/mcp
Authorisation server https://auth.memoryrouter.ai
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.memoryrouter.ai/mcp Verified 200
http (plaintext) http://mcp.memoryrouter.ai/mcp Inconclusive 405
MCP tools · 5 exposed · ~396 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
forget_all_memories ~103

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 a later turn. Permanently deletes every memory in the OAuth-selected vault. This cannot delete one memory; direct the user to the dashboard for item-level curation. Requires separate memories:delete authorization and destructive host confirmation.

NameTypeReqDescription
confirmationstringyesExact phrase the user must provide after being warned that deletion is permanent.
NameTypeReqDescription
deletedbooleanyes
messagestringyes
vaultRefstringyes

No examples provided.

memory_status ~45

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. Does not reveal the memory key.

Input schema present but exposes no named parameters.

NameTypeReqDescription
connectedbooleanyes
grantedScopesarrayyes
storagestringyes
totalMemoriesintegeryes
totalTokensintegeryes
vaultRefstringyes

No examples provided.

search ~73

Use this legacy compatibility alias when a client explicitly requests a tool named search. It searches the OAuth-selected MemoryRouter vault without modifying it. For normal ChatGPT recall, prefer search_memories; this tool does not provide citable item permalinks or Company Knowledge fetch support.

NameTypeReqDescription
querystringyesNatural-language search query.
NameTypeReqDescription
resultsarrayyes

No examples provided.

search_memories ~85

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 searches only the OAuth-selected vault and does not modify it.

NameTypeReqDescription
limitintegerMaximum number of relevant memories to return.
querystringyesA concise natural-language description of the past context to recall.
NameTypeReqDescription
countintegeryes
memoriesarrayyes
querystringyes

No examples provided.

store_memory ~90

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 vault; do not use it for silent conversation capture.

NameTypeReqDescription
contentstringyesThe concise fact, preference, decision, or outcome the user approved for storage.
tagsarrayOptional short category labels. These are preserved as provenance text until structured tags ship.
NameTypeReqDescription
acceptedbooleanyes
sourcestringyes
statusstringyes
vaultRefstringyes

No examples provided.