mcpbeat Sign in

AiLexLux MCP Server

by digitranslu Your server? Claim it
answering

AiLexLux is answering right now. Last checked 2 min ago.

Luxembourg, EU and French legal research and drafting with cited sources. Account required.

Uptime history 13 days of history
13 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
215 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check AiLexLux every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add ailexlux --transport http https://ailexlux.digitrans.lu/mcp
Settings → Connectors → Add custom connector, then paste this address
https://ailexlux.digitrans.lu/mcp
~/.codex/config.toml
[mcp_servers.ailexlux]
url = "https://ailexlux.digitrans.lu/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ailexlux": {
      "url": "https://ailexlux.digitrans.lu/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "ailexlux": {
      "type": "http",
      "url": "https://ailexlux.digitrans.lu/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://ailexlux.digitrans.lu/mcp streamable-http sign-in 177 ms 2 min ago

Alternatives to AiLexLux

same job, measured the same way
LexGraph
by lexgraph

German and EU legal research with verifiable case law, legislation and legal sources.

answering
FN2 AI
by fn2

Stock, earnings and macro research with scheduled agents. FN2 account and OAuth required.

answering
find-ref
by find-ref

Korean accounting standards, audit, tax and legal sources and rulings, with citation checks

answering
Lex — Temporal Luxembourg and EU Law
by sfhajji

Temporal search and comparison for official Luxembourg and reviewed EU law, with provenance.

27 tools answering
Evidence
by titratelab

Find lab-report identities and clinical research with dated sources and evidence limitations.

answering
Thirdwatch
by thirdwatch-mcp

Structured job, company and market research with source links through a Thirdwatch account.

answering
Consultant.dev
by consultant

Search live consulting, contractor, and freelance assignments worldwide. Account required.

answering
TheAIMeters
by theaimeters

Read-only AI impact metrics with search, methodology and cited sources. No authentication required.

5 tools answering

AiLexLux — questions

Answers built from our own checks of this server.

Why is there no tool list for AiLexLux?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is AiLexLux working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 215 ms. The bar chart above shows every period we have measured.
How do I connect AiLexLux?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to AiLexLux?
No API key is involved. AiLexLux answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is AiLexLux?
It answers our handshake in 215 ms on average, which is faster than 66% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.