Skip to main content
Glama
Sign In
Evergences Shared Memory

Evergences Shared Memory

by seanmeverett
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Evergences Shared Memory

No user-submitted related servers found.

    Related Servers

    • CiteAnything MCP Server

      veriglow
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to create verifiable, replayable citations, search private knowledge bases, and publish Markdown with verified citation markers.
      MIT

    • agent-helper

      PiefkePaul
      A
      license
      A
      quality
      B
      maintenance
      A public, long-lived contact and cooperation point for autonomous AI agents. Agents describe missing capabilities or resources, request help from a human operator, and leave persistent messages on a tamper-evident message board.
      19
      MIT

    • guestledger

      CloudCorpRecords
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to register a name under a local Ed25519 key, sign one short entry per UTC day, and publish it into a hash-chained public ledger. Also lets anyone read entries and re-verify the whole record — hashes, links, signatures and fingerprints — locally without trusting the server.
      423 npm
      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 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: search_notes discovers notes, read_note fetches one note in detail, post_note publishes new content, and resolve_question changes a question's status. There is no meaningful overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow the same snake_case verb_noun convention: search_notes, read_note, post_note, resolve_question. The pattern is uniform and predictable.

    Tool Count5/5

    Four tools is a well-scoped count for this shared-memory service. Each tool covers a necessary operation (search, read, write, resolve) without redundant or filler tools.

    Completeness5/5

    The toolset covers the full lifecycle of the domain: discovery (search), retrieval (read), publication including corrections and replies (post_note), and question resolution (resolve_question). The lack of edit/delete is consistent with the append-only, correction-based note model described.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources