ENYAL by Greenland AI

ai.enyal由 enyal.ai 發布官方發布者v0.1.2更新於 Oct 26, 2026

帳戶由 ENYAL 身份提供支援,記錄可驗證,無需信任我們。

AI 翻譯由 AI 模型根據下方的原文描述翻譯,可能有誤。

原文描述

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

已驗證Streamable HTTP可網頁執行資料庫知識與記憶安全與監控

概覽

ENYAL by Greenland AI 的託管 MCP 服務(mcp.enyal.ai),由 enyal.ai 發布;無需登入;Streamable HTTP;9 個工具。

暫無 AI 概覽:以下資訊來自註冊中心條目和服務本身。

發布者
enyal.ai
端點
mcp.enyal.ai
最近檢查

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 ENYAL by Greenland AI,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/ai.enyal%2Fenyal/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "enyal-by-greenland-ai": {
      "type": "http",
      "url": "https://mcp.enyal.ai/mcp"
    }
  }
}

工具

9

query_memory

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.

輸入參數plan必填include_chunks

get_entity

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

輸入參數node_idname_hash

get_timeline

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

輸入參數node_typevalid_to_beforevalid_from_after

render

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

輸入參數plan必填

verify_chunk

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.

輸入參數identifier必填

query_memory_content

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.

輸入參數plan必填include_chunks

get_entity_content

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

輸入參數node_idname_hash

get_timeline_content

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).

輸入參數node_typevalid_to_beforevalid_from_after

get_node_content

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).

輸入參數name_hashinclude_neighbours_depth

版本歷史

2
  1. v0.1.2最新Oct 26, 2026
  2. v0.1.0Sep 16, 2026

評分

已滿足適用檢查項的 72%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分

    請在註冊中心條目中發布圖示。

  • 文件15 分

    請宣告包含 README 的 GitHub 儲存庫,或在 OAuth 受保護資源後設資料中提供 resource_documentation。

  • 授權條款不適用

    託管服務按其提供方的條款使用,因此這裡不要求授權條款。此檢查項不計入百分比。