Talandor

What Talandor observed

MemoryRouter

https://mcp.memoryrouter.ai/mcp

Reachable

10 public tools listed

Server checked October 28

You can set this connector up in your assistant. The listed tools were not executed.

Address availability
Reachable
HTTP 200 was received.
MCP protocol
Exchange verified
Protocol 2026-07-28.
Public tools
10 public tools listed
These tools were listed, not executed.
Use in your assistant: not verified · authentication details
Authentication
Not detected
No authentication challenge was observed in this check.
Your assistant
Not verified
Talandor does not check the local setup in Cursor, ChatGPT, Claude, or Windsurf. Private tools were not verified. No tool call was executed.

What should I do next?

Still blocked in your assistant? Diagnose the symptom →

  1. Add the connector to your assistant

    Open the configuration guide below. Keep your existing connectors when adding this one.

  2. Check that the tools appear

    Open the connector in your assistant and check its available tools. Talandor has not tested that connection or executed those tools.

The tools still do not appear?

These are checks you can carry out. A public result does not identify a fault in your assistant.

  1. Check your client's MCP support

    Check your client's documentation for support of this remote HTTP endpoint and how to enable its tools. Local-server and remote-server configuration can differ.

  2. Check provider access

    If sign-in is requested, check the account and permissions in the assistant. An accessible public endpoint does not establish access to private tools.

  3. Read the error shown by the assistant

    Compare its configured address with this report, then use the provider's or assistant's official help. If you contact Talandor, share the error with tokens and private data removed.

Help and contact

Check details

Official Registry

Official Registry · ai.memoryrouter/memoryrouter · Publisher namespace: ai.memoryrouter

Catalog verified September 19

What changed

Public contract stable since
Last check · No semantic contract change since the previous complete snapshot.
Info

This public timeline shows the latest check, the last 24 hours, and the most recent important change. Watch keeps 30 days.

The notes above are for this connector.

Server-provided content. Tool names, descriptions and schemas below are copied from the MCP server. They may be in another language. Talandor does not translate or verify them.
Tools and declared exposure

Server annotations are declarations, not verified behavior.

Show 10 of 10 server-provided tool definitions
commit_reflections
Declared idempotent
Show server-provided details
Commit reflections
Server description (copied; language not verified)
Use this to complete a consolidation started with consolidate_memories. Submits the reflection entries you wrote for the checked-out batch. Each entry is standalone prose with an importance rating from 1 to 10. The server stores the reflections, links them to their source memories, and marks the sources consolidated. Safe to retry: committing the same batch twice returns the original result.
Input schema (server-provided preview — do not copy)
{
  "type": "object",
  "required": [
    "batch_id",
    "entries"
  ],
  "properties": {
    "entries": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "importance",
          "text"
        ],
        "properties": {
          "text": {
            "type": "string",
            "maxLength": 8000,
            "minLength": 1
          },
          "importance": {
            "type": "integer",
            "maximum": 10,
            "minimum": 1
          }
        },
        "additionalProperties": false
      },
      "maxItems": 100,
      "minItems": 1
    },
    "batch_id": {
      "type": "string",
      "minLength": 1
    }
  },
  "additionalProperties": false
}
consolidate_memories
Annotation present; effect not classified
Show server-provided details
Consolidate memories (checkout)
Server description (copied; language not verified)
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 available. Checks out a batch of unconsolidated memories from the connected vault under a 15 minute lease and returns their texts plus server instructions for writing reflection entries. Follow the returned instructions to write the entries, then call commit_reflections with the batch_id. Nothing is modified until commit.
Input schema (server-provided preview — do not copy)
{
  "type": "object",
  "properties": {
    "tier": {
      "enum": [
        1,
        2
      ],
      "type": "integer",
      "default": 1,
      "description": "1 consolidates raw memories into reflections; 2 consolidates reflections into high-level reflections."
    },
    "max_tokens": {
      "type": "integer",
      "default": 50000,
      "minimum": 1000,
      "description": "Token budget for the checked-out batch. Defaults to 50000. No connector-side cap."
    }
  },
  "additionalProperties": false
}
date_search_memories
Declared read-only
Show server-provided details
Search memories by date
Server description (copied; language not verified)
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 guide: tier 3 holds the highest-level consolidated reflections (identity, principles, what matters most), tier 2 holds reflections of specific meaningful events, tier 1 holds raw verbatim memories. Match filters to the question. Time-bounded 'most important things last month' questions: tiers [3], importance 8 or higher, generous max_tokens. Big-picture overviews of a period like 'what do you know about July': tiers [3] with no importance filter. Specific lookups in a window like 'find the decision about X': omit tiers to include all tiers and leave importance unset; a high importance filter hides the specific detail you are looking for. Specific meaningful events without raw noise: tiers [2] or [2, 3]. Exact verbatim detail: if the detail is not already in context, drill down by lineage: search tiers [3] to find the relevant thread, then use inspect_memory on the result to see the tier 2 reflections it consolidated, then inspect those to reach the raw memories underneath. Direct tiers [1] search works when you know exact wording to match. Mixing tiers is legitimate; adjust the importance threshold to the question rather than always setting it high. Only reflections (tiers 2 and 3) carry importance ratings. Omit query for a chronological review; include query to rank by relevance within the window. Resolve relative phrases like 'lately' to concrete ISO dates before calling. Reads only the OAuth-selected vault and does not modify it.
Input schema (server-provided preview — do not copy)
{
  "type": "object",
  "required": [
    "from"
  ],
  "properties": {
    "to": {
      "type": "string",
      "maxLength": 64,
      "minLength": 4,
      "description": "Window end, ISO 8601 date or datetime. Optional, defaults to now."
    },
    "from": {
      "type": "string",
      "maxLength": 64,
      "minLength": 4,
      "description": "Window start, ISO 8601 date or datetime (e.g. 2026-08-10 or 2026-08-10T00:00:00Z). Required. Must be a concrete date, not a relative phrase."
    },
    "query": {
      "type": "string",
      "maxLength": 2000,
      "minLength": 1,
      "description": "Optional relevance query. Omit for a pure chronological browse; include to rank results within the window."
    },
    "tiers": {
      "type": "array",
      "items": {
        "enum": [
          1,
          2,
          3
        ],
        "type": "integer"
      },
      "minItems": 1,
      "description": "Restrict results to these memory tiers. 3 highest-level consolidated reflections (identity, principles, what matters most), 2 reflections of specific meaningful events, 1 raw verbatim memories. Use [3] for broad 'most important' or big-picture questions, [2] or [2, 3] for specific meaningful events, [1] for exact verbatim detail when you know the wording to match; otherwise drill down from [3] with inspect_memory. Omit to search all tiers blended, the right default for specific lookups. Mixing tiers is fine. Only tiers 2 and 3 carry importance ratings.",
      "uniqueItems": true
    },
    "importance": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1,
      "description": "Minimum importance threshold, 1 to 10. Only reflections (tiers 2 and 3) carry ratings, so raw memories are excluded whenever this is set. Use 8 or higher with tiers [3] for broad 'most important' questions. Leave unset for general or specific searches; a high threshold hides relevant material."
    },
    "max_tokens": {
      "type": "integer",
      "maximum": 200000,
      "minimum": 1000,
      "description": "Token budget for returned results. Server default 50000; use a smaller value like 5000 for a quick look. When a page is truncated, continue with the returned next_to or next_from cursor."
    }
  },
  "additionalProperties": false
}
delete_memories
Declared destructive
Show server-provided details
Delete specific memories
Server description (copied; language not verified)
Use this only when the user explicitly asks to delete specific memories and confirms after seeing what will be deleted. Permanently deletes the identified memories from the connected vault by their ids from search or inspect results. Deleting a raw memory does not delete reflections built from it. This cannot be undone. For deleting everything, forget_all_memories is the separate whole-vault tool.
Input schema (server-provided preview — do not copy)
{
  "type": "object",
  "required": [
    "confirmation",
    "ids"
  ],
  "properties": {
    "ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 100,
      "minItems": 1,
      "description": "Memory ids (UUIDs) to permanently delete."
    },
    "confirmation": {
      "enum": [
        "DELETE SELECTED MEMORIES"
      ],
      "type": "string",
      "description": "Exact phrase the user must provide after being shown which memories will be deleted."
    }
  },
  "additionalProperties": false
}
forget_all_memories
Declared destructive
Show server-provided details
Delete all memories in connected vault
Server description (copied; language not verified)
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; use delete_memories for specific items. Requires separate memories:delete authorization and destructive host confirmation.
Input schema (server-provided preview — do not copy)
{
  "type": "object",
  "required": [
    "confirmation"
  ],
  "properties": {
    "confirmation": {
      "enum": [
        "DELETE ALL MEMORIES"
      ],
      "type": "string",
      "description": "Exact phrase the user must provide after being warned that deletion is permanent."
    }
  },
  "additionalProperties": false
}
inspect_memory
Declared read-only
Show server-provided details
Inspect memory lineage
Server description (copied; language not verified)
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 result, returns the lower-tier memories that reflection was built from, or, for a raw memory, which reflections it was consolidated into. Use repeatedly to drill down from a high-level reflection to the tier 2 reflections and raw memories beneath it. Read only.
Input schema (server-provided preview — do not copy)
{
  "type": "object",
  "required": [
    "memory_id"
  ],
  "properties": {
    "memory_id": {
      "type": "string",
      "maxLength": 36,
      "minLength": 36,
      "description": "A memory id (UUID) from a search result or a previous inspect."
    }
  },
  "additionalProperties": false
}
memory_status
Declared read-only
Show server-provided details
Check memory status
Server description (copied; language not verified)
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 (server-provided preview — do not copy)
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
search
Declared read-only
Show server-provided details
Search MemoryRouter knowledge
Server description (copied; language not verified)
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.
Input schema (server-provided preview — do not copy)
{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 2000,
      "minLength": 1,
      "description": "Natural-language search query."
    }
  },
  "additionalProperties": false
}
search_memories
Declared read-only
Show server-provided details
Search memories
Server description (copied; language not verified)
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. Tier guide: tier 3 holds the highest-level consolidated reflections (identity, principles, what matters most), tier 2 holds reflections of specific meaningful events, tier 1 holds raw verbatim memories. Match filters to the question. Broad 'most important things we have done' questions: tiers [3], importance 8 or higher, large limit such as 250. Big-picture overviews like 'what do you know about this area or period': tiers [3] with no importance filter. Specific lookups like 'find the decision about X': omit tiers to search all tiers blended and leave importance unset; a high importance filter hides the specific detail you are looking for. Specific meaningful events without raw noise: tiers [2] or [2, 3]. Exact verbatim detail: if the detail is not already in context, drill down by lineage: search tiers [3] to find the relevant thread, then use inspect_memory on the result to see the tier 2 reflections it consolidated, then inspect those to reach the raw memories underneath. Direct tiers [1] search works when you know exact wording to match. Mixing tiers is legitimate; adjust the importance threshold to the question rather than always setting it high. Only reflections (tiers 2 and 3) carry importance ratings. For time-window questions like 'what happened last week' or 'lately' use date_search_memories instead.
Input schema (server-provided preview — do not copy)
{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 5,
      "maximum": 250,
      "minimum": 1,
      "description": "Maximum number of relevant memories to return. Use a large limit such as 250 for broad 'most important things' questions over tiers [3]."
    },
    "query": {
      "type": "string",
      "maxLength": 2000,
      "minLength": 1,
      "description": "A concise natural-language description of the past context to recall."
    },
    "tiers": {
      "type": "array",
      "items": {
        "enum": [
          1,
          2,
          3
        ],
        "type": "integer"
      },
      "minItems": 1,
      "description": "Restrict results to these memory tiers. 3 highest-level consolidated reflections (identity, principles, what matters most), 2 reflections of specific meaningful events, 1 raw verbatim memories. Use [3] for broad 'most important' or big-picture questions, [2] or [2, 3] for specific meaningful events, [1] for exact verbatim detail when you know the wording to match; otherwise drill down from [3] with inspect_memory. Omit to search all tiers blended, the right default for specific lookups. Mixing tiers is fine. Only tiers 2 and 3 carry importance ratings.",
      "uniqueItems": true
    },
    "importance": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1,
      "description": "Minimum importance threshold, 1 to 10. Only reflections (tiers 2 and 3) carry ratings, so raw memories are excluded whenever this is set. Use 8 or higher with tiers [3] for broad 'most important' questions. Leave unset for general or specific searches; a high threshold hides relevant material."
    }
  },
  "additionalProperties": false
}
store_memory
Annotation present; effect not classified
Show server-provided details
Remember something
Server description (copied; language not verified)
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.
Input schema (server-provided preview — do not copy)
{
  "type": "object",
  "required": [
    "content"
  ],
  "properties": {
    "tags": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 64,
        "minLength": 1
      },
      "maxItems": 10,
      "description": "Optional short category labels. These are preserved as provenance text until structured tags ship."
    },
    "content": {
      "type": "string",
      "maxLength": 12000,
      "minLength": 1,
      "description": "The concise fact, preference, decision, or outcome the user approved for storage."
    }
  },
  "additionalProperties": false
}
Evidence and limitations

Method: anonymous Streamable HTTP probe. We never invoke a tool.

Attempted protocols: 2026-07-28

Protocol2026-07-28
TransportStreamable HTTP
AuthNo authentication challenge observed
EvidencePublic contract observed
Total latency391 ms
Response bytes21714

No diagnostic errors.

Observation history
Operational
· stable since
2026-07-28 · 10 tools · no change · 276 checks
Operational
2026-07-28 · 10 tools
Operational
2026-07-28 · 10 tools
Complete public contract · 2026-07-28 · 10 tools
b311394e9e2e
Complete public contract · 2026-07-28 · 10 tools
b311394e9e2e
Complete public contract · 2026-07-28 · 10 tools
b311394e9e2e

Deep monitoring eligibility

Eligible for deep monitoring

A complete public tools/list contract was observed, so a future deep-monitoring baseline can be compared safely.

A Watch starts from the payment section on this page, and only after a verified payment.

See public monitoring
Watch · recurring plan

Watch this MCP

Optional. Setting up the connector does not require Watch.

Full public-contract coverage: Availability, protocol, auth and public tool contract changes can be compared.

Full WatchAvailability, protocol, auth and public tool contract changes
Surface WatchAvailability, TLS, protocol and auth surface — no private tool diff

Early access currently activates this first endpoint; adding more endpoints up to the planned limit of five is not open in this deployment. Live checkout is open. A Watch activates only after a verified payment event; a browser return never starts monitoring.

Start Watch