Skip to main content
Glama
Sign In
@saihm/mcp-server-pro

@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
      B
      maintenance
      Zero-knowledge, self-hostable MCP server providing encrypted durable memory for AI agents, with tools to save, recall, search, list, and delete memories.
      472 npm
      69
      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.
      28 npm
      MIT

    • Hippocampus

      karrolcia
      A
      license
      Not graded
      quality
      B
      maintenance
      Open-source MCP memory server providing persistent, cross-platform context for AI tools via a knowledge graph with encrypted storage.
      12 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
      C
      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
    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.3/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool has a distinct primary action: remember, recall, forget, share, revoke_share, join, status, and governance propose/vote. The main complexity is that recall and remember each carry multiple modes (sharing lists, warm-start snapshots, version listing), but their core purposes remain separable.

    Naming Consistency4/5

    All tools use the saihm_ prefix and snake_case, with mostly verb-based names such as saihm_remember, saihm_forget, saihm_share, and saihm_revoke_share. Minor deviations exist: saihm_status is a noun, and governance tools use a noun_then_verb pattern (saihm_governance_propose, saihm_governance_vote).

    Tool Count5/5

    Nine tools is well-scoped for an encrypted persistent-memory service with sharing, session status, and governance hooks. Each tool maps to a meaningful operation, and the set is neither thin nor bloated.

    Completeness4/5

    The core memory lifecycle is covered: create/update (saihm_remember), read/list (saihm_recall), erase (saihm_forget), share/revoke, join, and status. Gaps are minor but notable: governance propose/vote are present yet unavailable, and identity import/export is referenced but not exposed as a tool here.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources