@saihm/mcp-server-pro

Official

by SAIHM-Admin

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Recall

saihm_recall

Read-onlyIdempotent

Retrieve and decrypt your stored memories at session start or when past context is needed. Filter by keyword, or load all; optionally read a shared cell securely without exposing plaintext to the server.

Instructions

Retrieve your memories from SAIHM and decrypt them in this process; the server never sees plaintext. Use this at the start of a session, or whenever past context is needed. Pass query to filter by keyword, or leave it out to load everything. To read a single cell another agent shared with you, pass their sharerPinnedAgentIdHashHex and sharerRecord together with the cellId; that path is read-only.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	No	Filter your OWN memories by keyword (empty = all). Ignored when reading a shared cell.
`cellId`	No	The shared cell id to read. Required when reading a shared cell.
`shareEntries`	No	With the share events feed on, also return every entry of the share map; without it, only its summary.
`sharerRecord`	No	The SHARER's published identity record (hex fields). Required with sharerPinnedAgentIdHashHex.
`sharerPinnedAgentIdHashHex`	No	Read a cell shared TO you: the SHARER's agentIdHash (hex), pinned out-of-band. When set, sharerRecord and cellId are also required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`shared`	Yes
`memories`	Yes
`shareStates`	No
`sharedTruncated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.10.0Sep 17, 2026

addedInput schema / properties / shareEntries

Added value: +{
+  "description": "With the share events feed on, also return every entry of the share map; without it, only its summary.",
+  "type": "boolean"
+}

addedOutput schema / properties / memories / items / properties / commitment
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / memories / items / properties / grant
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / shareStates

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "asOf": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "complete": {
+      "type": "boolean"
+    },
+    "counts": {
+      "additionalProperties": false,
+      "properties": {
+        "ended": {
+          "type": "number"
+        },
+        "erased": {
+          "type": "number"
+        },
+        "live": {
+          "type": "number"
+        },
+        "stale": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "live",
+        "stale",
+        "ended",
+        "erased"
+      ],
+      "type": "object"
+    },
+    "entries": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "cellId": {
+            "type": "string"
+          },
+          "commitment": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "copiesInvalidBefore": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "endedAt": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "endedBy": {
+            "anyOf": [
+              {
+                "enum": [
+                  "event",
+                  "reconciliation"
+                ],
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "expiryEpoch": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "grant": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "scope": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "senderVerified": {
+            "type": "boolean"
+          },
+          "seq": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "sharer": {
+            "type": "string"
+          },
+          "status": {
+            "enum": [
+              "live",
+              "stale",
+              "ended",
+              "erased"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "sharer",
+          "cellId",
+          "status",
+          "grant",
+          "scope",
+          "expiryEpoch",
+          "seq",
+          "commitment",
+          "senderVerified",
+          "endedAt",
+          "endedBy",
+          "copiesInvalidBefore"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "since": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "startedAt": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "stopped": {
+      "anyOf": [
+        {
+          "enum": [
+            "unsupported",
+            "tier",
+            "erased"
+          ],
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "since",
+    "complete",
+    "asOf",
+    "stopped",
+    "startedAt",
+    "counts"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedv0.2.2Aug 31, 2026

addedOutput schema / properties / shared

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "cellId": {
+        "type": "string"
+      },
+      "expiryEpoch": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "scope": {
+        "type": "string"
+      },
+      "sharer": {
+        "type": "string"
+      },
+      "verified": {
+        "const": false,
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "sharer",
+      "cellId",
+      "scope",
+      "expiryEpoch",
+      "verified"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / sharedTruncated
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "count",
-  "memories"
-]New value: +[
+  "count",
+  "memories",
+  "shared",
+  "sharedTruncated"
+]

First observedv0.2.1Jul 29, 2026

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable behavioral context beyond those: decryption happens locally, the server never sees plaintext, and the shared-cell path is read-only. This enriches the agent's understanding without contradicting any annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and well-structured: core operation first, then usage timing, then filtering behavior, then the special shared-cell path. Every sentence contributes distinct, useful information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema, annotations, and full schema coverage, the description covers invocation timing, filtering, and the shared-cell special case. Nothing essential is missing for an agent to decide when and how to call this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful parameter relationships: query is ignored when reading a shared cell, and sharerPinnedAgentIdHashHex, sharerRecord, and cellId are used together. This goes beyond the individual field descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action ('Retrieve your memories from SAIHM') and adds meaningful detail about local decryption. It distinguishes the normal memory-recall path from the shared-cell read path, and the name/title are not merely restated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells the agent when to use it ('at the start of a session, or whenever past context is needed') and explains the query/all-memories choice. It does not explicitly list when-not-to-use cases or name sibling alternatives, so it falls just short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server