LexLint.io

Developersbeta

Search the docs /
Docs menu

Get started

Quickstart Install: Claude Code Install: Codex Install: other clients API keys

Concepts

How a run works The app profile The severity model What a run does not say

Tools

check_access claim_trial_key set_profile run_lint get_law resolve_domain_jurisdiction submit_feedback upload_lint_run

Guides

A whole run, end to end Console TestPack in CI

Reference

Endpoint and transport lexlint.yml schema Errors Changelog

Help

Support and feedback

Reference

Endpoint and transport

One address over streamable HTTP, stateless, with one header that matters.

The endpoint

https://mcp.lexlint.io/mcp

Any client that speaks streamable HTTP works: the server is stateless and holds no session of its own, so nothing has to be kept between calls. The configuration each client wants, and the two fields that differ from one client to the next, are on the other clients page.

Headers

HeaderWhat it carries
X-API-KeyYour UnGovr Open Data key. Sent empty, it connects without one, which is enough to list the tools. check_access then names the ways to get a key.
Authorization: BearerAn OAuth access token. An MCP client that signs in sends it.
MCP-Protocol-Version2025-06-18 or later receives outputSchema and structuredContent. A client that names an older revision, or none, is served the same tools without them.

The browser lane

https://mcp.lexlint.io/rpc answers the same calls for a page in a browser, the Console included. It is rate limited at the edge, so a page should not call it in a loop: one call every two seconds is plenty. An agent should use /mcp.