Skip to main content
Glama

ENYAL by Greenland AI

Server Details

Encrypted memory, knowledge graph and provable history for AI agents. ENYAL is the trust infrastructure for autonomous AI: identity, encrypted memory, and BSV-anchored proofs. Archived records are Merkle-batched and anchored to a permanent cryptographic ledger, and any record's inclusion proof can be checked by anyone, with no account.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 9 tools

Disambiguation4/5

The structure vs. content split (get_entity/get_entity_content, get_timeline/get_timeline_content, query_memory/query_memory_content) is a clear, learnable pattern that lets an agent pick correctly. However, render is currently described as doing exactly what query_memory does (structure-only, identical shape), and get_node_content overlaps with query_memory's include_neighbours_depth, creating two soft redundancies.

Naming Consistency4/5

Most tools follow a consistent snake_case verb_noun pattern with a reliable _content suffix convention for decrypted variants, which is easy to reason about. The deviations are render (bare verb, no noun) and the somewhat differently shaped verify_chunk, but these are minor and still readable.

Tool Count5/5

Nine tools is well-scoped for a read-oriented encrypted knowledge-graph server, with each pair of structure/content tools earning its place. There is no bloat and no sense of a thin surface.

Completeness4/5

The surface covers structure retrieval, decrypted content, neighborhood traversal, temporal views, structured querying, and public verification, forming a coherent read lifecycle. The notable gap is any write/ingestion or entity-listing/search operation, meaning agents must already hold name_hashes rather than discover entities by name.

Publisher details

Operator
Greenland AI Limited
Operator website
https://enyal.ai
Vendor relationship
First-party
Trust center
Not available
Restrictions
Unknown

Available Tools

9 tools
get_entityA
Read-onlyIdempotent
Inspect

Get one entity's STRUCTURE by name_hash (SHA-256 of the normalised name). No content.

Inputs: node_id, name_hash.

get_entity_contentA
Read-onlyIdempotent
Inspect

Get one entity's DECRYPTED content by name_hash (SHA-256 of the normalised name). Content scope required (403 otherwise).

Inputs: node_id, name_hash.

get_node_contentA
Read-onlyIdempotent
Inspect

Get a node's DECRYPTED content by name_hash PLUS its connected nodes' content (neighbour depth, default 1; 0–5). Same plan schema as the structure tools. Content scope required (403).

Inputs: name_hash, include_neighbours_depth.

get_timelineA
Read-onlyIdempotent
Inspect

Temporally-ordered STRUCTURE view, optionally filtered by node_type and an ISO8601 date range. No content.

Inputs: node_type, valid_to_before, valid_from_after.

get_timeline_contentA
Read-onlyIdempotent
Inspect

Temporally-ordered DECRYPTED content view, optionally filtered by node_type + an ISO8601 date range. Same plan schema as get_timeline. Content scope required (403 otherwise).

Inputs: node_type, valid_to_before, valid_from_after.

query_memoryA
Read-onlyIdempotent
Inspect

Execute a structured query plan over your encrypted knowledge graph. Returns STRUCTURE ONLY (node_type, name_hash, relationships, chunk_ids, timestamps) — never content.

Plan schema:
  {
    "entity_filters": [{"node_type": <type>} | {"name_hash": <sha256-hex>}],
    "edge_filters":   [{"relationship": <rel>, "direction": "out"|"in"|"both"}],
    "temporal_bounds":{"valid_from_after": <ISO8601>, "valid_to_before": <ISO8601>},
    "limit": <int <= 200>,
    "include_neighbours_depth": <0-5>
  }
node_type in {entity, concept, decision, person, organisation, event, source, synthesis}.
relationship in {references, contradicts, supports, supersedes, caused_by, related_to,
part_of, informed_by, led_to, verifies}. Account scope is enforced server-side; it cannot be
set from the plan.

Inputs: plan (required), include_chunks.

query_memory_contentA
Read-onlyIdempotent
Inspect

Execute a structured query plan and return DECRYPTED memory CONTENT (node names, summaries, properties; edge evidence + endpoint names) alongside structure. SAME plan schema as query_memory. REQUIRES a memory:read:content-scoped token — a structure-only token is rejected (403) by ENYAL. Account scope is enforced server-side; it cannot be set from the plan.

Inputs: plan (required), include_chunks.

renderC
Read-onlyIdempotent
Inspect

Render a structured query as a STRUCTURE-ONLY result set (β = structure; identical shape to query_memory). Reserved for richer rendering when content access (γ) lands.

Inputs: plan (required).

verify_chunkA
Read-onlyIdempotent
Inspect

Look up one identifier in ENYAL's PUBLIC verification index (relays GET /api/v1/verify/lookup/{id}; no decryption). ENYAL's answer is returned unchanged: found, and for a chunk or proof its anchor_status with bsv_tx_id; for a txid, chain_status. degraded:true means a source could not be checked (inconclusive, not an absence). ENYAL's route needs no key; calling it through this server still needs your eyl_ bearer, like every tool call. An id that is not a UUID or hex is refused (invalid_id) and nothing is sent.

Inputs: identifier (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      A
      maintenance
      Persistent, consensus-validated institutional memory for AI agents. Gives LLMs real memory that survives across sessions - validated through BFT consensus, not just dumped to a file.
      38
      23 npm
      265
      Apache 2.0
    • F
      license
      A
      quality
      B
      maintenance
      Enables LLMs to read and write the BSV social graph with an on-chain identity, OS-keychain wallet, and 38 tools for posts, replies, follows, messages, payments, profiles, and more, with every write broadcast as a real BSV mainnet transaction visible across 50+ shared apps.
      42
      16 npm
      1
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources