Skip to main content
Glama

Related Servers

Alternatives to emem

  • A
    license
    A
    quality
    B
    maintenance
    Local, searchable project memory for AI coding agents. Markdown source of truth, MCP interface, safe structured updates
    3
    15
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to interact with the Planet API for satellite imagery ordering, subscriptions, and data management through natural language.
    18
    Apache 2.0

Related Servers

  • F
    license
    B
    quality
    C
    maintenance
    Enables AI agents to query verifiable physical-world ground truth for any point on Earth — water availability, seismic and space-weather hazard, ground stability, and resource indications — with every answer backed by a Bitcoin-anchored provenance record that can be independently verified. It also lets agents check whether an Earth-science hypothesis has already been tested, list documented nulls and retractions, and run bounded controlled tests that return UNTESTABLE rather than fabricate a result.
    11
    -
  • F
    license
    Not graded
    quality
    D
    maintenance
    Gives AI a virtual body to explore real locations on Earth using authentic terrain, weather, sky, radio, wildlife, and cultural data, with tools for walking, observing, asking about history, and collecting souvenirs—fully offline-capable.
    4
    -
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables users to pin lessons, claims, and open questions about physical objects to the places they live, then resume that thread later from any phone or assistant through three tools: observe, ask, and commit. Matching runs on host-authored text descriptions and user-named places, so no images are stored and identity survives switching devices, apps, or models.
    3
    Apache 2.0
  • A
    license
    A
    quality
    C
    maintenance
    Give AI agents cryptographically signed proof of web observations: Ed25519-signed proof packets (HTTP status, page title, body SHA-256, DNS, TLS) for any public URL.
    1
    MIT

TDQS

A4.1/5.0

Scored across 18 tools

Disambiguation3/5

The core lifecycle tools are distinct, but several boundaries overlap: emem_ask, search, fetch and emem_recall all retrieve signed facts, while fetch and emem_memory_token_resolve both dereference fact citations. emem_intent and emem_tools are meta-wrappers that can route to the same operations, so descriptions help but do not eliminate misselection risk.

Naming Consistency4/5

Most tools use a predictable emem_ snake_case prefix, and the names are readable despite mixing noun- and verb-oriented forms. The two unprefixed tools, search and fetch, are clear exceptions that slightly break the pattern.

Tool Count3/5

Eighteen tools is heavy for a listed MCP surface, especially when it includes both primitive operations and multiple high-level wrappers such as emem_ask, emem_intent and emem_tools. The breadth is justified by the domain, but the set feels borderline over-scoped rather than tightly curated.

Completeness3/5

The citation lifecycle is well covered: locate, recall, mint tokens, bundle, resolve, verify and guard. However, the listed surface omits several primitives explicitly referenced by the descriptions, such as trajectory, polygon recall, diff, edges and inferences, so agents may hit dead ends unless they can access /mcp/full.

Maintenance

ActivityActive
ResponsivenessUsually handled