Skip to content

ENYAL by Greenland AI

by enyal.ai · remote · no sign-in to list tools · v0.1.0 · published by ai.enyal

ENYAL by Greenland AI — encrypted identity & memory for AI agents (query, recall, provenance)

Changes · 4

9 tools: 4 change things and 5 only read.

Scanned Oct 21, 2026

2 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http enyal https://mcp.enyal.ai/mcp

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "query_memory" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "query_memory" says "query": a word for reading.

    What this check looks for
  • The server marks "query_memory_content" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "query_memory_content" says "query": a word for reading.

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

9 tools

Changes things 4Claude Code: ask
  • query_memoryExecute a structured query plan over your encrypted knowledge graph.1 finding

    Why it is in this group

    • The name "query_memory" says "query": a word for reading.
    • The description's first verb is "execute": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "query_memory" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "query_memory" says "query": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • query_memory_contentExecute a structured query plan and return DECRYPTED memory CONTENT (node names, summaries, properties; edge evidence + endpoint names) alongside structure.1 finding

    Why it is in this group

    • The name "query_memory_content" says "query": a word for reading.
    • The description's first verb is "execute": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "query_memory_content" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "query_memory_content" says "query": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • renderRender a structured query as a STRUCTURE-ONLY result set (β = structure; identical shape to query_memory).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Render a structured query as a STRUCTURE-ONLY result set (β = structure; identical shape to query_memory). Reserved for richer rendering when content access (γ) lands.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • verify_chunkLook up one identifier in ENYAL's PUBLIC verification index (relays GET /api/v1/verify/lookup/{id}; no decryption).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 5Claude Code: allow
  • get_entityGet one entity's STRUCTURE by name_hash (SHA-256 of the normalised name).No findings

    Why it is in this group

    • The name "get_entity" says "get": a word for reading.
    Description, as the server wrote it
    Get one entity's STRUCTURE by name_hash (SHA-256 of the normalised name). No content.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_entity_contentGet one entity's DECRYPTED content by name_hash (SHA-256 of the normalised name).No findings

    Why it is in this group

    • The name "get_entity_content" says "get": a word for reading.
    Description, as the server wrote it
    Get one entity's DECRYPTED content by name_hash (SHA-256 of the normalised name). Content scope required (403 otherwise).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_node_contentGet a node's DECRYPTED content by name_hash PLUS its connected nodes' content (neighbour depth, default 1; 0–5).No findings

    Why it is in this group

    • The name "get_node_content" says "get": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_timelineTemporally-ordered STRUCTURE view, optionally filtered by node_type and an ISO8601 date range.No findings

    Why it is in this group

    • The name "get_timeline" says "get": a word for reading.
    Description, as the server wrote it
    Temporally-ordered STRUCTURE view, optionally filtered by node_type and an ISO8601 date range. No content.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_timeline_contentTemporally-ordered DECRYPTED content view, optionally filtered by node_type + an ISO8601 date range.No findings

    Why it is in this group

    • The name "get_timeline_content" says "get": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http enyal https://mcp.enyal.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__enyal__get_entity",
      "mcp__enyal__get_timeline",
      "mcp__enyal__get_entity_content",
      "mcp__enyal__get_timeline_content",
      "mcp__enyal__get_node_content"
    ],
    "ask": [
      "mcp__enyal__query_memory",
      "mcp__enyal__render",
      "mcp__enyal__verify_chunk",
      "mcp__enyal__query_memory_content"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as enyal. Review it before you use it.