Remote MCP · Endpoint

LexAtlas MCP server

No. LexAtlas answered an MCP handshake 39 minutes ago.

UpLast checked 39 minutes ago

Server URL

https://api.lexatlas.creatora.app/mcp

The last check completed an MCP handshake.

Registry name
app.creatora.lexatlas/lexatlas-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
361 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Current law as data for AI: search, read and verify statutes and citations. CIS countries first.
Listing
From the official MCP registry (active).
Recent checks of LexAtlas
CheckedResultHandshake
39 minutes agoHandshake completed361 ms
3 days agoHandshake completed527 ms
13 days agoCredentials required—
13 days agoCredentials required—
15 days agoCredentials required—
16 days agoCredentials required—
17 days agoCredentials required—
18 days agoCredentials required—
18 days agoCredentials required—
20 days agoCredentials required—
22 days agoCredentials required—
25 days agoCredentials required—
27 days agoCredentials required—

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with LexAtlas and makes no claim about it beyond what these checks measured.