Esheria Regulatory Intelligence

io.github.esherialabs由 GitHub 帳號 esherialabs 發布v1.2.2更新於 Nov 11, 2026

Citation-backed regulatory intelligence tools for explicit multi-jurisdiction packs

已驗證Streamable HTTP可網頁執行知識與記憶安全與監控商業與電商

概覽

AI 產生的概覽

附引用的法規情報服務:讓助理依明確的司法管轄包查詢義務、罰則、適用性與變更事件。

可以做什麼
  • 檢查服務健康與就緒狀態,並依管轄區列出、檢視與比較法規包
  • 取得所選包的義務、適用性、罰則、申報行事曆、證據與稽核中繼資料
  • 驗證主張、追溯引用,並查詢法規項目之間的關聯
  • 追蹤版本、差異與變更事件,並匯出附 trace ID 的有限結果
  • 營運者權杖可增加受範圍限制的監控、圖譜與客戶寫入操作,每次都需要明確確認
適用情境
當助理需要針對特定管轄區與法規包提供有出處的法規答案時使用,例如整理義務、核對罰則或長期追蹤變化。適合合規、法務營運與稽核研究等必須保留引用、版本與限制說明的場景。它不能取代專業法律意見。
執行需求
可使用帶 OAuth 的託管遠端端點,或以 uvx 從 esheria Python 套件啟動本機 stdio 程序。需要儀表板建立的資料權杖,透過 ESHERIA_API_KEY(或別名 ESHERIA_API_TOKEN)提供,也可作為 bearer 權杖或 X-API-Key 標頭;ESHERIA_API_BASE_URL 用於設定 API 基底位址。需要能連線至 Esheria API 的網路。
安裝前請注意
API 金鑰是計費憑證:不要寫入提交紀錄、shell 歷史或程序清單,優先使用環境變數而非命令列參數。唯讀權杖僅有 regulatory:read;monitoring:write、graph:write、customer:write 等寫入範圍會啟用改變狀態的操作,應最小授權並保持短期有效。查詢內容、包 ID 與結果會傳送至 Esheria 託管服務,輸出屬於法規情報而非法律意見。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Esheria Regulatory Intelligence,將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

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

交給代理程式安裝

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

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

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

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "mcpServers": {
    "esheria-regulatory-intelligence": {
      "type": "http",
      "url": "https://mcp.esheria.ai/mcp"
    }
  }
}

README

Esheria CLI And MCP

Installable command-line and MCP tools for the Esheria Regulatory Pack API.

Global, citation-backed regulatory intelligence for explicit published packs. Discover current readiness, select the intended jurisdiction and pack, and preserve citations, versions, limitations, and trace IDs across CLI, Python, and MCP workflows. Esheria provides regulatory intelligence, not legal advice.

The package exposes two commands:

bash
esheria --helpesheria-mcp --helpesheria mcp serve --help

Version 1.2.2 is the production/stable public release. The CLI, Python client, and MCP software distributed in the esheria Python package are licensed under the Apache License 2.0. Hosted API/MCP access, regulatory data, service outputs, and Esheria trademarks are not licensed under Apache-2.0; they remain governed by the Esheria Terms of Service, Privacy Policy, and any applicable customer agreement. See LICENSE and NOTICE for the exact boundary.

CLI Quickstart

  1. Create a data API token in the Esheria dashboard.
  2. Install the command. pipx is recommended because it keeps command-line tools isolated from project dependencies:
bash
pipx install esheria

If you do not use pipx, use normal pip:

bash
python3 -m pip install esheria
  1. Configure your shell. Put these in your terminal for a one-off test, or in ~/.zshrc, ~/.bashrc, or your shell profile to keep them:
bash
export ESHERIA_API_BASE_URL="https://api.esheria.ai"export ESHERIA_API_KEY="<client-api-key>"

PowerShell:

powershell
$env:ESHERIA_API_BASE_URL = "https://api.esheria.ai"$env:ESHERIA_API_KEY = "<client-api-key>"

ESHERIA_API_TOKEN is also accepted as an alias when ESHERIA_API_KEY is unset.

Do not commit API keys. The CLI and MCP server read credentials from environment variables or command-line flags and redact API key values from diagnostic output. Prefer the environment variable: --api-key can be exposed through shell history or the operating-system process list.

  1. Confirm the API is reachable:
bash
esheria --versionesheria health --format jsonesheria ready --format json
  1. Discover packs, choose a domain_pack_id, then pass that pack ID to pack-specific commands:
bash
esheria packs list --format jsonexport ESHERIA_PACK_ID="UK-DATA-PROTECTION-PRIVACY"esheria packs inspect "$ESHERIA_PACK_ID" --format jsonesheria packs versions "$ESHERIA_PACK_ID" --format jsonesheria packs diff "$ESHERIA_PACK_ID" --format jsonesheria packs change-events "$ESHERIA_PACK_ID" --format jsonesheria obligations list "$ESHERIA_PACK_ID" --limit 3 --format jsonesheria penalties list "$ESHERIA_PACK_ID" --limit 5 --format jsonesheria legal-review audit "$ESHERIA_PACK_ID" --limit 5 --format json

Output flags can be placed globally or on a leaf command:

bash
esheria --format json packs listesheria packs list --format json

Use esheria --help and <group> --help to discover the full command tree. The CLI includes source-watch operations, graph coverage/rebuild operations, workspace-scoped customer lifecycle commands, and workspace/token/billing management commands in addition to the read workflows above.

Workspace, token, and billing commands require a management token. Normal dashboard-created and OAuth connector tokens carry only regulatory:read. State-changing regulatory workflows require an explicitly created operator data token with one or more of monitoring:write, graph:write, or customer:write; regulatory:read alone is rejected. For example:

bash
esheria tokens create \  --name "Monitoring operator" \  --scope regulatory:read \  --scope monitoring:write \  --pack UK-DATA-USE-AND-ACCESS

The dashboard remains the recommended place for self-serve workspace, token, billing, and subscription administration. Keep operator tokens short-lived and grant only the scopes and pack entitlements they require.

The CLI and MCP server are catalog-first: users list packs and then call tools with the explicit pack ID they want. ESHERIA_DEFAULT_PACK_ID is an optional client preference, not a server-side jurisdiction default.

The CLI reports the API's readiness labels, limitations, citations, and trace IDs; preserve them in downstream workflows. Published packs may represent a reviewed subset of the full legal corpus, and evaluator-gated claim verification is not available for every pack. Esheria output is regulatory intelligence, not legal advice or a substitute for qualified counsel.

Hosted MCP

Production MCP uses the hosted Esheria endpoint:

text
https://mcp.esheria.ai/mcp

Use this endpoint for normal customer onboarding. It avoids local Python, uvx, virtual environments, and package discovery on the user's machine.

Claude Directory hosts use OAuth. Other agent hosts send a dashboard-created Esheria data token as a bearer token or X-API-Key. The hosted MCP server introspects the credential before initialization and calls the Regulatory Pack API with it, so billing, pack entitlements, trace IDs, and published-only behavior remain centralized. Invalid and management-only credentials cannot enumerate tools.

Codex MCP

Set the token where Codex can read it:

bash
export ESHERIA_API_KEY="<client-api-key>"

Edit ~/.codex/config.toml and add:

toml
[mcp_servers.esheria]url = "https://mcp.esheria.ai/mcp"bearer_token_env_var = "ESHERIA_API_KEY"

Restart Codex, then call esheria_health, esheria_ready, and esheria_list_packs.

Local MCP Fallback

For local development, or for agent hosts that do not support remote MCP URLs, you can run the stdio server yourself:

bash
esheria-mcp serve --stdio

Operator-only HTTP transport command:

bash
ESHERIA_API_BASE_URL="https://api.esheria.ai" \  esheria-mcp serve --http --host 127.0.0.1 --port 8081 --path /mcp

Production is already deployed at https://mcp.esheria.ai/mcp; end users should not run this command.

The hosted OAuth profile exposes a read-only 20-tool catalog for health, readiness, pack discovery, obligations, applicability, claim verification, versions, diffs, change events, filing calendars, evidence, penalties, audit metadata, relationship queries, exports, and citation context. Normal API data tokens expose 29 safe read/read-like tools. Operator data tokens add only mutations authorized by monitoring:write, graph:write, and/or customer:write, up to the complete 37-tool catalog. Every mutation also requires confirm=true; OAuth Directory sessions remain read-only.

The hosted service uses the official MCP SDK and current Streamable HTTP. Successful tools mirror bounded JSON in text content and structuredContent, with trace_id and mcp truncation metadata. Use the API or CLI when a complete large export is needed.

Use stdio only for hosts that do not support remote MCP URLs:

toml
[mcp_servers.esheria]command = "uvx"args = ["--from", "esheria", "esheria-mcp", "serve", "--stdio"]env = { ESHERIA_API_BASE_URL = "https://api.esheria.ai", ESHERIA_API_KEY = "<client-api-key>" }

Claude Code

Use Claude Code's remote MCP setup when your installed version exposes it:

  • URL: https://mcp.esheria.ai/mcp
  • Authorization: Bearer <client-api-key>

If your Claude Code version only supports local stdio MCP servers, run this fallback once from a terminal:

bash
claude mcp add --scope user --transport stdio \  --env ESHERIA_API_BASE_URL=https://api.esheria.ai \  --env ESHERIA_API_KEY=<client-api-key> \  esheria -- uvx --from esheria esheria-mcp serve --stdio

Then run:

bash
claude mcp list

Start or restart Claude Code and ask it to use the Esheria MCP tools.

Claude Desktop

Use Claude Desktop's remote MCP setup when your installed version exposes it:

  • URL: https://mcp.esheria.ai/mcp
  • Authorization: Bearer <client-api-key>

If your Claude Desktop version only supports local stdio MCP servers, use the fallback below.

Open the Claude Desktop MCP config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Add or merge this object:

json
{  "mcpServers": {    "esheria": {      "command": "uvx",      "args": ["--from", "esheria", "esheria-mcp", "serve", "--stdio"],      "env": {        "ESHERIA_API_BASE_URL": "https://api.esheria.ai",        "ESHERIA_API_KEY": "<client-api-key>"      }    }  }}

Restart Claude Desktop after saving the file.

來源:README.md,提交 e089c9c

工具

0
該伺服器需要 API 金鑰等憑證,因此 SourceWeft 無法在沒有憑證的情況下讀取其工具,也未收錄。

版本歷史

1
  1. v1.2.2最新Sep 16, 2026

評分

已滿足適用檢查項的 85%

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

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

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分