Skip to main content
Glama
20vision

mymemory-mcp

by 20vision
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to mymemory-mcp

No user-submitted related servers found.

    Related Servers

    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.1/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools have distinct purposes: get_context (retrieve full vault), search (find specific entries), and propose (add new entries). While get_context and search both read data, their purposes are clearly separated (bulk fetch vs. targeted lookup), and propos e is clearly a write operation. No meaningful ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent mymemory_<verb> pattern: get_context, search, propose. The verbs are uniform and descriptive, and each name clearly signals its operation (retrieval, lookup, and write). The mymemory_ prefix consistently scopes the namespace.

    Tool Count3/5

    Three tools is on the thin side but understandable for a personal memory vault: fetch, search, and write. The scope is narrow enough that three tools could work, though one might expect an explicit update/delete mechanism. It's at the lower boundary of reasonable.

    Completeness3/5

    The vault supports retrieval (get_context), search, and creation (propose, gated by PENDING approval). However, there's no tool to update or delete existing active entries, nor to approve the pending queue, meaning maintenance of the vault is delegated entirely to the human in the app. This leaves some lifecycle gaps beyond the core read/write flow.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources