Skip to content

LexOpti MCP server

The LexOpti MCP server lets an AI assistant act in a LexOpti organization for one member, with that member’s role. It serves the professionals who use LexOpti; to let an assistant read this documentation while it writes your integration, use the documentation MCP server. To connect an assistant, follow connect an assistant to LexOpti.

Property Value
Endpoint https://app.lexopti.com/mcp
Transport Model Context Protocol over Streamable HTTP
Authorization OAuth 2.1, Client ID Metadata Documents, no open dynamic registration
Audit every action is recorded in the organization’s audit trail as coming from the assistant
  1. The assistant calls https://app.lexopti.com/mcp without a token. LexOpti answers 401 with the address of its protected resource metadata (RFC 9728), https://app.lexopti.com/.well-known/oauth-protected-resource/mcp, which names the authorization server.
  2. The assistant identifies itself by the URL of its client metadata document (Client ID Metadata Documents, CIMD). LexOpti has no open dynamic client registration: an assistant without CIMD support, such as Cursor or Copilot Studio, uses a client LexOpti registers for it.
  3. LexOpti opens in your browser. You sign in, choose the organization the assistant acts for, and approve the access it asks for.
  4. The assistant gets a token for the MCP server alone: it cannot call the public API, and a public API token cannot call the MCP server.
Scope What the assistant can do
lexopti:read Read clients, cases, classifications, alerts and checks, and preview a launch or a case.
lexopti:write Launch checks, create cases and review alerts.

The assistant sees only the tools its scopes allow. When it calls a write tool with lexopti:read alone, LexOpti answers 403 insufficient_scope and the assistant asks you to authorize again with both scopes. A member with a read-only role can never write, whatever the scopes.

Tool Scope What it does
lexopti_search_clients read Finds clients of the organization by name (a full name in either order), company name or SIREN, newest first, 10 by default and 20 at most.
lexopti_get_client_status read Reads a client’s vigilance level, where its analyses stand, its open alerts and its last validated risk assessment.
lexopti_get_case_summary read Reads a case: its type, status, clients with your references, its other parties and their roles, vigilance level, the risk level a member validated, where its classification stands and how many alerts are pending.
lexopti_get_classification read Reads the classification of a client or a case as you saved it: its state, score, level, last validation and the questions still unanswered; never answers or validates it for you, and never returns the suspicion axis.
lexopti_list_alerts read Lists the organization’s alerts, newest first, for one client or one status, a page at a time.
lexopti_get_check_run read Reads where a check stands and the status of each source it ran.
lexopti_preview_check read Shows what launching a client’s checks would screen, the dossier it is charged to and its credits, without launching anything.
lexopti_preview_case read Shows what creating a case (a dossier) for existing clients, with its natures and parties, would cost in credits, without creating anything.
lexopti_launch_check write Launches a client’s checks after their preview, charged to the client’s dossier.
lexopti_create_case write Creates the case after its preview, once you confirmed its cost in LexOpti’s form; without a form, only proposes it for you to create in LexOpti.
lexopti_acknowledge_alert write Records your review of an alert (reviewed, dismissed or confirmed) with your reason, or proposes it for you to validate in LexOpti.

An alert reaches the assistant as fields (source, publisher, level, category, date and link), never as the text of the page that raised it. The server answers in English; the assistant answers you in your language.

The assistant can never confirm a launch, a creation or a review on your behalf.

Launching a check. The assistant first calls lexopti_preview_check and shows you who will be screened, the dossier charged and the credits it costs. The preview returns a preview_token, signed by LexOpti, valid 5 minutes and bound to you, the organization, the assistant, the client and those figures. lexopti_launch_check refuses a missing, expired or altered token, and refuses it when the entities to screen changed since the preview, or what it costs, or when the credits no longer cover the launch. Then:

  • if your assistant can show a form (MCP elicitation), LexOpti asks you there to confirm the launch, and declining launches nothing;
  • otherwise the launch rests on your assistant’s own approval of the call, which proves nothing when it is set to « always allow ».

LexOpti records how you confirmed with the check: confirmed_via is elicitation or not_elicited. The same preview launches once: calling again returns the check already launched. An assistant launches at most 20 checks an hour for you; beyond that, launch in LexOpti.

Creating a case. The assistant first calls lexopti_preview_case with the case’s clients, natures and parties, and shows you what it costs: one credit per tranche of five people or companies, one at least, as LexOpti’s « Nouveau dossier » screen charges it. The preview returns a preview_token of its own (never valid for a check), valid 5 minutes and bound to you, the organization, the assistant, exactly those arguments and that cost. lexopti_create_case refuses a missing, expired or altered token, other arguments than those previewed, a cost that changed, or credits that no longer cover it. Then:

  • if your assistant can show a form, LexOpti asks you there to confirm the creation and its cost, and declining creates nothing;
  • otherwise the assistant only proposes the case: nothing is created nor charged until you, or another member, open the link it gives you, https://app.lexopti.com/proposals/<id>. It opens LexOpti’s « Nouveau dossier » screen filled from the proposal, its price on the button: check it, change it if needed, and create it there. A proposal is kept 7 days.

The same preview creates, or proposes, once: calling again returns the same case. Creations count in the same 20 an hour as the launches.

Reviewing an alert. Your decision and your reason are yours, never the assistant’s:

  • if your assistant can show a form, you enter the decision and the reason there, and the review applies at once, replacing any earlier one;
  • otherwise the assistant only proposes the review. Nothing changes on the alert until you, or another member, validate or reject it in LexOpti, under « Assistant proposals » on the client’s page. The assistant gives you the link, https://app.lexopti.com/proposals/<id>.
Limit Value
Calls per member and assistant 120 a minute, then 429
Calls per client address 300 a minute, then 429
Check launches and case creations per member and assistant 20 an hour
preview_token valid 5 minutes, launches or creates once
Request body 64 KiB, then 413
JSON-RPC batches refused, 400
lexopti_search_clients 10 results by default, 20 at most
lexopti_list_alerts pages of 20 by default, 50 at most

A preview reports incomplete_identity (identity fields to complete in LexOpti first) or insufficient_credits (the client’s dossier needs more credits than the organization holds) when nothing can be launched.