Use the canonical endpoint or package.
Follow the maintained documentation instead of copying stale configuration from a directory listing.
MCP integration
Use Esheria regulatory intelligence in Cursor.
Configure the remote Streamable HTTP MCP URL or the local stdio package fallback while keeping credentials outside project files.
Integration contract
Keep setup simple without weakening the product boundary.
Create credentials explicitly.
Generate a dashboard token or complete OAuth consent; credentials never travel in marketing URLs or analytics.
Select the intended pack.
Discover current readiness and choose the jurisdiction and pack your workflow actually uses.
Preserve response context.
Carry citations, versions, limitations, readiness, errors, and trace IDs into the host experience.
Respect scopes and entitlements.
Client surfaces do not authorize requests; the server enforces tokens, packs, features, rates, credits, and write scopes.
Route high-risk outputs to review.
Unsupported, ambiguous, or legally sensitive conclusions still require qualified human judgement.
Related developer routes