com.lexifina/lexifina
Lexifina
Is the Lexifina MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-11.
Search, review, edit and redline your Lexifina legal documents; work on matters, clients and time.
needs auth probed 2026-11-15 · unchanged since 2026-11-11 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"Connect Lexifina to continue"}- Endpoint
- https://mcp.lexifina.com/mcp (streamable-http)
- Host
- mcp.lexifina.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.lexifina.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server app.lexifina.com, PKCE S256, grants authorization_code, refresh_token.
Scopes documents:read matters:read search:read documents:write agents:read agents:write agents:review.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://lexifina.com/connectors
- Registry
- active, updated 2026-11-10 · registry entry
Compare this server with others.
More servers
Servers that mention lexifina or documents or clients.
- Global law com.lexifina/global-law · alive
- AutEng MCP - Markdown Publishing & Document Share Links ai.auteng/mcp · alive
- Dreamlit ai.dreamlit/mcp · alive
- ai.extend/extend · needs auth
- ai.ezel/ezel · needs auth
- ai.filegraph/document-processing · not found
- FinStat ai.finstat/finstat · needs auth
- Harmny ai.harmny/harmny · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.