Skip to main content
Glama
SAIHM-Admin

@saihm/mcp-server-pro

Official
by SAIHM-Admin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @saihm/mcp-server-pro

No user-submitted related servers found.

    Related Servers

    • memlawb

      Twigpine
      A
      license
      Not graded
      quality
      C
      maintenance
      Zero-knowledge, self-hostable MCP server providing encrypted durable memory for AI agents, with tools to save, recall, search, list, and delete memories.
      60
      MIT

    • Engram

      Kalyan-Deva
      A
      license
      Not graded
      quality
      D
      maintenance
      A local-first memory MCP server that enables storing, searching, and managing personal memories with hybrid keyword and semantic recall, all on-device.
      6 npm
      MIT

    • Hippocampus

      karrolcia
      A
      license
      Not graded
      quality
      A
      maintenance
      Open-source MCP memory server providing persistent, cross-platform context for AI tools via a knowledge graph with encrypted storage.
      7 npm
      13
      AGPL 3.0

    • pce-memory

      CAPHTECH
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for context-aware memory and retrieval with hybrid search, dual-phase memory, and boundary-first security.
      3
      MIT

    • amem

      apertomemory
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to persistently remember user preferences and context through client-side encrypted vaults, ensuring memory is portable and private across different MCP clients.
      1
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.2/5.0

    Scored across 9 tools

    Disambiguation4/5

    Core memory operations (remember/recall/forget) and access operations (share/revoke_share) have clearly distinct purposes with no real overlap. The main wrinkle is that remember, recall, and forget each overload a warmStart parameter for snapshot management, muddying their boundaries, and the two governance stubs are present but always error.

    Naming Consistency4/5

    All tools share a predictable saihm_ prefix, which aids grouping. However, the convention is slightly mixed: most are simple verbs (remember, recall, forget, share, join) or verb_noun (revoke_share), while the governance tools flip to noun_verb (governance_propose, governance_vote).

    Tool Count5/5

    Nine tools is well-scoped for a memory-plus-sharing-plus-governance domain, with each tool covering a distinct capability. Nothing feels redundant or padded aside from two intentionally inert governance stubs.

    Completeness3/5

    CRUD for memory cells (remember/recall/forget), sharing (share/revoke_share), status, and onboarding (join) are covered. But the join description references an 'export-identity' flow that has no corresponding tool, and the two governance tools are non-functional stubs, leaving notable gaps in the advertised surface.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources