Lintsure
Compliance readiness checks for code: EU AI Act, GDPR, SOC 2, ISO 27001. Local. Not legal advice.
Description from the maker (original English)
Citation-backed regulatory intelligence tools for explicit multi-jurisdiction packs
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
ESHERIA_API_BASE_URL, ESHERIA_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.esheria.ai/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"esheria": {
"command": "uvx",
"args": [
"esheria",
"mcp",
"serve",
"--stdio"
],
"env": {
"ESHERIA_API_BASE_URL": "your-value",
"ESHERIA_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add --transport http esheria https://mcp.esheria.ai/mcpclaude mcp add esheria --env ESHERIA_API_BASE_URL=your-value --env ESHERIA_API_KEY=your-value -- uvx esheria mcp serve --stdioFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"esheria": {
"url": "https://mcp.esheria.ai/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"esheria": {
"command": "uvx",
"args": [
"esheria",
"mcp",
"serve",
"--stdio"
],
"env": {
"ESHERIA_API_BASE_URL": "your-value",
"ESHERIA_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"esheria": {
"type": "http",
"url": "https://mcp.esheria.ai/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"esheria": {
"type": "stdio",
"command": "uvx",
"args": [
"esheria",
"mcp",
"serve",
"--stdio"
],
"env": {
"ESHERIA_API_BASE_URL": "your-value",
"ESHERIA_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.esheria.ai/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
ESHERIA_API_BASE_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account esherialabs, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: ESHERIA_API_KEY
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (1.2.2) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Lintsure, Premium Data MCP Server, Patents Trademarks Ip MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Compliance readiness checks for code: EU AI Act, GDPR, SOC 2, ISO 27001. Local. Not legal advice.
Government contracts, business registration, FDA recalls and product-price data as agent tools.
Patent search, inventor search, patents-by-assignee and full patent detail as agent tools.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
pipx is 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
~/.zshrc, ~/.bashrc, or your shell profile to keep them:export ESHERIA_API_BASE_URL="https://api.esheria.ai"
export ESHERIA_API_KEY=" "
PowerShell:
$env:ESHERIA_API_BASE_URL = "https://api.esheria.ai"
$env:ESHERIA_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.
esheria --version
esheria health --format json esheria ready --format json
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 --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.
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.
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.
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 = " " }
Use Claude Code's remote MCP setup when your installed version exposes it:
https://mcp.esheria.ai/mcpBearer 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= \ 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.
Use Claude Desktop's remote MCP setup when your installed version exposes it:
https://mcp.esheria.ai/mcpBearer If your Claude Desktop version only supports local stdio MCP servers, use the fallback below.
Open the Claude Desktop MCP config file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonAdd 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": " " } } } }
Restart Claude Desktop after saving the file.