Skip to content

ENYAL by Greenland AI MCP server

ai.enyal/enyalenyal.aistreamable-httpv0.1.2Scanned

Accounts are powered by ENYAL identity, and records are verifiable without trusting us.

9 tools: 4 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 4 write, 5 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the ENYAL by Greenland AI MCP server can do

The ENYAL by Greenland AI MCP server is published by enyal.ai, a domain the MCP Registry verified. It has 9 tools. It can create or change data (4 tools: query_memory, render, verify_chunk and query_memory_content), but cannot delete data. 5 tools only read.

1 tool brings in text other people can write (verify_chunk).

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 9, 2026, version 0.1.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

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).Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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 5Show 5 read-only tools
  • 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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:25 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.enyal.ai/.well-known/oauth-protected-resource
Authorization servers
https://mcp.enyal.ai/
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.enyal.ai/mcp: tools/list returned 9 tools to an anonymous client, including query_memory (write), render (write), verify_chunk (write), query_memory_content (write)

    What this check looks for

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

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http enyal https://mcp.enyal.ai/mcp
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as enyal. Review it before you use it.

Capability tags behind 1 rule
  • mcp__enyal__verify_chunk untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.enyal/enyal/verify?hash=c4c802db37f31592878f6f74c1a2cbedce6e330d3e0310c02700f53f38c43781" | jq -e '.changed == false'

Pinned hash c4c802db37f3, from Nov 9, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.enyal/enyal/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.enyal/enyal
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.enyal/enyal.svg)](https://radar.anlyon.com/servers/ai.enyal/enyal)

Source: MCP Registry. Synced Oct 26, 2026, 21:17 UTC.

ENYAL by Greenland AI MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the ENYAL by Greenland AI MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 4 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the ENYAL by Greenland AI MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the ENYAL by Greenland AI MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the ENYAL by Greenland AI MCP server have?

9 tools: 4 write, 5 read. query_memory, render, verify_chunk, query_memory_content, get_entity, get_timeline, get_entity_content, get_timeline_content and 1 more.

Does the ENYAL by Greenland AI MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the ENYAL by Greenland AI MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the ENYAL by Greenland AI MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 9, 2026.