Skip to main content
Glama
SAIHM-Admin

saihm-mcp-server (standards client)

by SAIHM-Admin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to saihm-mcp-server (standards client)

No user-submitted related servers found.

    Related Servers

    • synapse-layer by SynapseLayer

      synapse-layerofficial

      SynapseLayer
      A
      license
      B
      quality
      A
      maintenance
      MCP-native persistent memory for AI agents. Stores and retrieves encrypted memories with Trust Quotient scoring, cross-agent handover protocol, and immutable audit trail. 13 tools. Remote endpoint available.
      13
      56 PyPI
      13
      Apache 2.0

    • CP Memory

      CJhuochai
      A
      license
      C
      quality
      A
      maintenance
      Local-first, governable long-term memory for AI agents. Provides SQLite-backed storage, cross-session recall, and traceable memory corrections through a standard MCP interface.
      40
      25 PyPI
      1
      MIT

    • rmbr

      SRock44
      A
      license
      A
      quality
      A
      maintenance
      Embedded memory and retrieval engine for AI agents, providing local-first memory with MCP support for multi-agent access control.
      3
      32 PyPI
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool maps to a distinct action: remember/forget/recall cover the memory lifecycle, share/revoke_share cover sharing, and governance_propose/vote cover governance, while status is uniquely diagnostic. There is no meaningful overlap between any pair of tools.

    Naming Consistency4/5

    All tools share the saihm_ prefix and use snake_case, but the suffix pattern is uneven: some are bare verbs (remember, forget, recall, share), others are object-first (governance_propose, governance_vote), and one is verb-object (revoke_share). This is readable and predictable enough, though not perfectly consistent.

    Tool Count5/5

    With 8 tools, the server is well-scoped and each tool has a clear role across three related subdomains: persistent memory, sharing, and governance. This is a comfortable size that avoids both bloat and thinness.

    Completeness4/5

    The memory lifecycle is essentially covered (create/read/delete), and sharing has both grant and revoke. The governance portion lacks a way to list or inspect open proposals, and there is no direct get-memory-by-id, but agents can work around these gaps using recall or status.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources