
Esheria Regulatory Intelligence
io.github.esherialabsPublished by GitHub account esherialabsv1.2.2Updated Nov 11, 2026
Citation-backed regulatory intelligence tools for explicit multi-jurisdiction packs
Overview
Citation-backed regulatory intelligence: lets an assistant look up obligations, penalties, applicability and change events for explicit jurisdiction packs.
- What you can do
- Check service health and readiness, and list, inspect and compare regulatory packs by jurisdiction
- Retrieve obligations, applicability, penalties, filing calendars, evidence and audit metadata for a chosen pack
- Verify claims, follow citations and query relationships between regulatory items
- Track versions, diffs and change events, and export bounded results with trace IDs
- Operator tokens add scoped write actions for monitoring, graph and customer workflows, each requiring explicit confirmation
- When to use it
- Use it when an assistant needs sourced regulatory answers for a specific jurisdiction and pack, such as mapping obligations, checking penalties or tracking changes over time. It suits compliance, legal-operations and audit research where citations, versions and limitations must be preserved. It is not a substitute for qualified legal counsel.
- Requirements
- Either the hosted remote endpoint with OAuth, or a local stdio process run with uvx from the esheria Python package. A dashboard-created Esheria data token is needed, supplied as ESHERIA_API_KEY (or the ESHERIA_API_TOKEN alias) or as a bearer token or X-API-Key header; ESHERIA_API_BASE_URL sets the API base. Network access to the Esheria API is required.
Installation
In SourceWeft
- Open Esheria Regulatory Intelligence in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.esherialabs%2Fesheria/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"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:
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
- Create a data API token in the Esheria dashboard.
- Install the command.
pipxis recommended because it keeps command-line tools isolated from project dependencies:
If you do not use pipx, use normal pip:
- Configure your shell. Put these in your terminal for a one-off test, or in
~/.zshrc,~/.bashrc, or your shell profile to keep them:
PowerShell:
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.
- Confirm the API is reachable:
- Discover packs, choose a
domain_pack_id, then pass that pack ID to pack-specific commands:
Output flags can be placed globally or on a leaf command:
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:
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:
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:
Edit ~/.codex/config.toml and add:
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:
Operator-only HTTP transport command:
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:
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:
Then run:
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:
Restart Claude Desktop after saving the file.
Source: README.md at commit e089c9c
Tools
0Version history
1- v1.2.2LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts