Skip to main content
Glama
Sign In
echocache

echocache

by kskurtveit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to echocache

No user-submitted related servers found.

    Related Servers

    • SuperBased Observer

      superbasedapp
      F
      license
      Not graded
      quality
      A
      maintenance
      Local MCP server that lets your AI coding agent query its own cross-tool project history - file/command freshness, past test failures, cost & token spend, cache status, and session handoff - over stdio, 100% local, no telemetry.
      58
      -

    • echo-cache

      SanjoyDat1
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Semantic caching MCP server for AI agent tool calls, providing exact and similarity-based cache lookup, store, invalidation, and metrics via MCP tools.
      -

    • memanchor

      AfridaMehanaz
      A
      license
      A
      quality
      C
      maintenance
      A local MCP server that lets coding agents persist decisions, conventions and gotchas across sessions and recall them with ranked search. Each memory is anchored to the files it describes, so recall flags it as stale when that code changes, and secrets are redacted before anything is stored.
      5
      2
      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.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a clearly distinct operation: exact-match lookup, storing new entries, semantic search, graph traversal, invalidation, and analytics. Even though cache_query and cache_related both deal with connected content, the descriptions make their different access patterns unambiguous.

    Naming Consistency4/5

    All tools share a consistent cache_ prefix and mostly use a verb as the second element: get, set, query, invalidate, stats. cache_related is the one outlier since 'related' is not a verb, but the overall pattern is still highly predictable.

    Tool Count5/5

    Six tools is well-scoped for a cache server: read, write, semantic access, graph traversal, invalidation, and statistics. Each tool earns its place without redundancy or bloat.

    Completeness4/5

    The cache lifecycle is well covered: exact lookup, storage with derived-from tracking, semantic retrieval, related-entry traversal, invalidation with cascade, and stats. Minor gaps like bulk clearing or listing all entries could be useful but are not essential for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources