mcp server
Esheria Regulatory Intelligence
Citation-backed regulatory intelligence tools for explicit multi-jurisdiction packs
Description as published by the maintainer. Source
- version 1.2.2
- active
active — Most recent push to the repository was 2026-07-15.
What this server can do
The server requires authentication before it will list its tools (HTTP 401). We do not hold an account for it, so its functions are unknown to us.
Endpoint status observed on . Source: https://mcp.esheria.ai/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-07-15 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 1.2.2 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-15 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | Apache-2.0 | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-07-15 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp endpoint status | auth_required | The server requires authentication before it will list its tools (HTTP 401). We do not hold an account for it, so its functions are unknown to us. | as of probe | mcp.esheria.ai |
Where to get it
Related, by what their authors tagged them
-
OpenCaseLaw — Swiss Caselaw, Statutes & Doctrine
— last commit 2026-08-06, shares legal-data
1M+ Swiss court decisions, statutes & doctrine with citation graph (DE/FR/IT). CC0, free, 42 tools.
-
io.github.365xbusiness/vigo-mcp
— last commit 2026-02-24, shares regulatory-intelligence
AI-powered Hong Kong SFC regulatory intelligence. Bilingual EN/ZH compliance queries.
-
io.github.aa0101181514/tw-legal-rag
— last commit 2026-08-05, shares legal-tech, python-cli
Citation-guarded retrieval over 22M Taiwan court judgments and administrative interpretations
-
Django ORM Lens
— last commit 2026-08-05, shares python-cli
Django ORM static analysis MCP. Models, relations, migrations, indexes, signals, N+1.
-
cloud-audit
— last commit 2026-07-21, shares python-cli
AWS security scanner with attack chain detection, IAM privilege escalation, and fixes
-
Scope (AEC) - Preview
— last commit 2026-07-30, shares legal-tech
AEC subcontractor vendor procurement plumbing layer. Preview - V3 launches 2027.
-
Scope (Claims) - Preview
— last commit 2026-07-30, shares legal-tech
Insurance claims-side vendor procurement (IMEs, IA, surveillance). Preview - V2 launches Q3 2026.
-
bid.scope/healthcare
— last commit 2026-07-30, shares legal-tech
Healthcare vendor-services MCP. Preview. Available after legal, claims, and AEC are live.
-
Scope (Legal)
— last commit 2026-07-30, shares legal-tech
Dispatch litigation work to legal-services vendors from any MCP-compatible AI workflow.
-
bid.scope/pharma
— last commit 2026-07-30, shares legal-tech
Pharma vendor-services MCP. Preview. Available after legal, claims, and AEC are live.
These share tags the maintainers applied themselves, such as legal-data, regulatory-intelligence, legal-tech, python-cli. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: compliance-api, legal-data, legal-tech, mcp-server, python-cli, regulatory-intelligence.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json