LexProtocol — EU AI Act Compliance
Independent, cryptographically signed attestation records for AI agent actions.
What it can do
What data it sees
Do you need an account
No: the server works without sign-in
Independent, cryptographically signed attestation records for AI agent actions. Every call produces a timestamped, tamper-evident record you can cite as evidence in an audit trail — not a self-reported log, and not a compliance certification. Useful for EU AI Act documentation; not a substitute for legal review. Enforcement live since August 2, 2026.
What it does
LexProtocol signs and timestamps AI agent actions to an independently verifiable ledger. Call attest_action before or after a regulated action to get back a signed attestation ID and citation string you can include in your audit trail. This is evidence of what happened, not a determination that the action was compliant.
Tools
attest_action— Sign and timestamp an AI agent action, returning a verifiable attestation ID and citation string. Register first (register_agent) for 100 free attestations.classify_ai_system— A preliminary, non-binding indication of which EU AI Act risk-tier language (minimal/limit
Requires a local install: run the server on your machine, then point your client at it.
How to connect
How to connect LexProtocol — EU AI Act Compliance to Claude
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
This server runs locally: it is wired up through the client config, and the project documentation carries the steps.
How to connect LexProtocol — EU AI Act Compliance to ChatGPT
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
This server runs locally: it is wired up through the client config, and the project documentation carries the steps.
How to connect LexProtocol — EU AI Act Compliance to Cursor
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
This server runs locally: it is wired up through the client config, and the project documentation carries the steps.
Tools not fetched yet: the server requires sign-in; the list appears after a manual check.