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

      Gitlawb
      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.
      58
      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.
      16 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.
      10 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
    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 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: join, remember, recall, forget, share, revoke_share, status, governance_propose, governance_vote. No overlapping functionality; even share and revoke_share are explicit opposites.

    Naming Consistency5/5

    All tools follow a consistent 'saihm_' prefix and use snake_case with a verb_noun or noun_verb pattern (e.g., saihm_remember, saihm_governance_propose). The pattern is uniform across the entire surface.

    Tool Count5/5

    9 tools is well within the ideal range and each tool covers a distinct operation in the memory lifecycle and governance. No redundancy or bloat; the count is appropriate for the server's scope.

    Completeness5/5

    The tool set covers the full lifecycle: join, remember (create/update), recall (read), forget (delete), share/revoke_share (access control), status (monitoring), and governance propose/vote. No obvious gaps for the stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources