MCP server de Esheria Regulatory Intelligence
✓ VerificadoProporciona inteligencia regulatoria respaldada por citas y datos de cumplimiento multijurisdiccionales a través de paquetes publicados explícitos.
También conocido como esherialabs/esheria-python, esheria-python, esheria
- Stars
- 0
- Herramientas
- —
- Descargas, 30 días
- 100
- Última versión
- 1.2.2
- Último commit
- 15 jul 2026
- Licencia
- Apache-2.0
¿Qué es Esheria Regulatory Intelligence MCP?
Esheria Regulatory Intelligence es un MCP server. Proporciona inteligencia regulatoria respaldada por citas y datos de cumplimiento multijurisdiccionales a través de paquetes publicados explícitos.
Resumen generado a partir del README del proyecto
Acerca del MCP server de Esheria Regulatory Intelligence
Los profesionales de cumplimiento y desarrolladores pueden acceder a inteligencia regulatoria respaldada por citas a través de este servicio para gestionar datos multijurisdiccionales. Al conectarse al endpoint alojado o ejecutar un servidor stdio local, los usuarios pueden interactuar con paquetes publicados explícitos para descubrir su estado de preparación actual y rastrear cambios regulatorios. El sistema requiere una API key de Esheria o credenciales OAuth para funcionar, las cuales pueden proporcionarse mediante variables de entorno o bearer tokens.
El conjunto de herramientas proporciona acceso a un catálogo de información regulatoria, incluyendo obligaciones, sanciones y calendarios de presentación. Dependiendo de los permisos del token, los usuarios pueden acceder a entre 20 y 37 herramientas diferentes. Mientras que los tokens estándar permiten leer datos como versiones de paquetes y eventos de cambio, los tokens de operador con scopes específicos como monitoring:write habilitan flujos de trabajo que modifican el estado. Esta inteligencia está diseñada para preservar citas, versiones e IDs de rastreo en flujos de trabajo de CLI, Python y MCP para garantizar la trazabilidad de los datos.
Qué puedes hacer con él
- 1Monitorear cambios regulatoriosLos desarrolladores pueden usar el servidor para identificar diferencias entre versiones o rastrear eventos de cambio recientes dentro de un paquete específico.
- 2Auditar obligaciones de cumplimientoLos usuarios pueden recuperar listas de obligaciones legales y sanciones asociadas para evaluar la preparación regulatoria.
- 3Verificar afirmaciones regulatoriasEl sistema permite la verificación de afirmaciones y la recuperación del contexto de las citas para respaldar la inteligencia regulatoria.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar Esheria Regulatory Intelligence MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar Esheria Regulatory Intelligence MCP en Claude Code
$ claude mcp add --env 'ESHERIA_API_KEY=<YOUR_ESHERIA_API_KEY>' esheria-python -- uvx esheriaInstalar Esheria Regulatory Intelligence MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"esheria-python": {
"command": "uvx",
"args": [
"esheria"
],
"env": {
"ESHERIA_API_KEY": "<YOUR_ESHERIA_API_KEY>"
}
}
}
}Instalar Esheria Regulatory Intelligence MCP en VS Code
.vscode/mcp.json
{
"servers": {
"esheria-python": {
"type": "stdio",
"command": "uvx",
"args": [
"esheria"
],
"env": {
"ESHERIA_API_KEY": "<YOUR_ESHERIA_API_KEY>"
}
}
}
}Instalar Esheria Regulatory Intelligence MCP en VS Code CLI
$ code --add-mcp '{"name":"esheria-python","type":"stdio","command":"uvx","args":["esheria"],"env":{"ESHERIA_API_KEY":"<YOUR_ESHERIA_API_KEY>"}}'Instalar Esheria Regulatory Intelligence MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"esheria-python": {
"command": "uvx",
"args": [
"esheria"
],
"env": {
"ESHERIA_API_KEY": "<YOUR_ESHERIA_API_KEY>"
}
}
}
}Instalar Esheria Regulatory Intelligence MCP en Codex
$ codex mcp add esheria-python --env 'ESHERIA_API_KEY=<YOUR_ESHERIA_API_KEY>' -- uvx esheriaInstalar Esheria Regulatory Intelligence MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.esheria-python] command = "uvx" args = ["esheria"] [mcp_servers.esheria-python.env] ESHERIA_API_KEY = "<YOUR_ESHERIA_API_KEY>"
Instalar Esheria Regulatory Intelligence MCP en Gemini CLI
$ gemini mcp add -s user -e 'ESHERIA_API_KEY=<YOUR_ESHERIA_API_KEY>' esheria-python uvx -- esheriaInstalar Esheria Regulatory Intelligence MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"esheria-python": {
"command": "uvx",
"args": [
"esheria"
],
"env": {
"ESHERIA_API_KEY": "<YOUR_ESHERIA_API_KEY>"
}
}
}
}Configuración
ESHERIA_API_KEYObligatorioSecretoDashboard-created Esheria data token
ESHERIA_API_BASE_URLEsheria API base URL
ESHERIA_PACK_ID
| Nombre | Descripción | Tipo |
|---|---|---|
| ESHERIA_API_KEY | Dashboard-created Esheria data token | ObligatorioSecreto |
| ESHERIA_API_BASE_URL | Esheria API base URL | |
| ESHERIA_PACK_ID | — |
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesibleesherialabs/esheria-python is public and reachablegithub.com/esherialabs/esheria-python ↗Aprobado
- El paquete indica este repositorio como su origenesheria names esherialabs/esheria-python as sourcepypi.org/project/esheria/ ↗Aprobado
- Procedencia de la compilación (atestación de Sigstore)Sigstore attestation for esheriapypi.org/project/esheria/ ↗Aprobado
- Licencia de código abierto (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-07-15github.com/esherialabs/esheria-python ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo popular package one edit away from esheriaAprobado
- No hay avisos críticos en el paquete ni en sus dependencias32 resolved dependencies checked; no critical advisoryosv.dev ↗Aprobado
- Sin instrucciones ocultas para el modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPHTTPS endpoint answered 401 (sign-in required)Aprobado
README
Ver en GitHubEsheria 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:
esheria --help
esheria-mcp --help
esheria 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
- Create a data API token in the Esheria dashboard.
- Install the command.
pipxis recommended because it keeps command-line tools isolated from project dependencies:
pipx install esheria
If you do not use pipx, use normal pip:
python3 -m pip install esheria
- Configure your shell. Put these in your terminal for a one-off test, or in
~/.zshrc,~/.bashrc, or your shell profile to keep them:
export ESHERIA_API_BASE_URL="https://api.esheria.ai"
export ESHERIA_API_KEY="<client-api-key>"
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.
- Confirm the API is reachable:
esheria --version
esheria health --format json
esheria ready --format json
- Discover packs, choose a
domain_pack_id, then pass that pack ID to pack-specific commands:
esheria packs list --format json
export ESHERIA_PACK_ID="UK-DATA-PROTECTION-PRIVACY"
esheria packs inspect "$ESHERIA_PACK_ID" --format json
esheria packs versions "$ESHERIA_PACK_ID" --format json
esheria packs diff "$ESHERIA_PACK_ID" --format json
esheria packs change-events "$ESHERIA_PACK_ID" --format json
esheria obligations list "$ESHERIA_PACK_ID" --limit 3 --format json
esheria penalties list "$ESHERIA_PACK_ID" --limit 5 --format json
esheria legal-review audit "$ESHERIA_PACK_ID" --limit 5 --format json
Output flags can be placed globally or on a leaf command:
esheria --format json packs list
esheria 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:
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:
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:
export ESHERIA_API_KEY="<client-api-key>"
Edit ~/.codex/config.toml and add:
[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:
esheria-mcp serve --stdio
Operator-only HTTP transport command:
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:
[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:
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:
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:
{
"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.
Preguntas sobre Esheria Regulatory Intelligence MCP
¿Cómo agrego Esheria Regulatory Intelligence MCP a Claude Code?
Ejecuta claude mcp add --env 'ESHERIA_API_KEY=<YOUR_ESHERIA_API_KEY>' esheria-python -- uvx esheria en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego Esheria Regulatory Intelligence MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Es Esheria un sustituto del asesoramiento legal?
No, Esheria proporciona inteligencia regulatoria, no asesoramiento legal.
¿Cómo configuro la Esheria CLI?
Puedes configurar tu shell exportando las variables de entorno ESHERIA_API_BASE_URL y ESHERIA_API_KEY.
¿Cuál es la diferencia entre los tokens normales y los tokens de operador?
Los tokens normales solo tienen permisos de regulatory:read, mientras que los tokens de operador permiten flujos de trabajo que cambian el estado con scopes como monitoring:write, graph:write o customer:write.