saihm-mcp-server (standards client)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAIHM_AUTH_HEADER | Yes | The Authorization header value (typically Bearer token) | |
| SAIHM_ENDPOINT_URL | Yes | The SAIHM operator endpoint URL (HTTPS required, except localhost) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| saihm_rememberA | Store information to SAIHM persistent encrypted memory. Use this when an agent or user wants a fact, decision, or piece of context to persist across sessions. |
| saihm_recallA | Retrieve memories from the SAIHM encrypted store; the operator decrypts and returns plaintext, this client holds no keys. Use this at the start of a session or whenever past context is needed; pass a keyword to filter, or leave empty to load all. |
| saihm_forgetA | Cryptographically erase a memory (GDPR Art. 17 erasure). Use this only to permanently and irreversibly delete a stored memory by its cell id; this cannot be undone. |
| saihm_statusA | Show SAIHM session status (PRS, BFSI, storage by tier, sharing, PHI), as far as the operator reports them — a non-custodial operator cannot see stored-byte totals. Use this to check the agent identity, reputation, storage, and sharing state of the current SAIHM session. |
| saihm_shareA | Create a sharing contract over one or more shards — type is 'temporary', 'permanent' or 'syndicate'. Use this to grant another agent access to specific memories. |
| saihm_revoke_shareA | Revoke an existing sharing contract by its contractId. Use this to withdraw a grantee's access previously granted with saihm_share. |
| saihm_governance_proposeA | Submit a gSAIHM-governance proposal. Scope MUST be 'emission_param' or 'protocol_upgrade'. Use this to open a protocol governance vote. |
| saihm_governance_voteA | Cast a vote on an open gSAIHM-governance proposal. Vote weight is derived from gSAIHM balance at proposal.snapshotEpoch. Use this to approve or reject an open proposal by its proposalId. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| saihm_session_bootstrap | Load your SAIHM persistent memory at the start of a session, before other work. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct operation: memory lifecycle (remember/forget/recall), session status, sharing contracts (share/revoke_share), and governance (propose/vote). There is no meaningful overlap or ambiguity between tools.
All tools share the consistent 'saihm_' prefix, which signals the same domain. Minor deviations exist: some are bare verbs (saihm_remember, saihm_status) and governance tools use noun-verb ordering (saihm_governance_propose) rather than the verb-noun pattern seen in saihm_revoke_share.
Eight tools is well-scoped for a memory, sharing, and governance client. Each tool covers a distinct capability without redundancy or bloat.
Core memory operations (store, retrieve, delete), sharing lifecycle, and governance voting are covered. Minor gaps exist, such as no tool to list open sharing contracts or enumerate governance proposals, but these are workable from the provided surface.