Home / MCP registry index / io.github.mcp-dir/legalone-mcp

LegalOne

io.github.mcp-dir/legalone-mcp in the official MCP registry. Endpoint https://api.mcp.ai/p_legalone. Source: github.com/mcp-dir/legalone-mcp.

The registry describes it as: Wrapper for the official LegalOne API (Thomson Reuters / Novajus, Premium package): lawsuits and lit

We read its 45 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http legalone-mcp https://api.mcp.ai/p_legalone

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "legalone-mcp": {
      "url": "https://api.mcp.ai/p_legalone"
    }
  }
}

VS Code

code --add-mcp '{"name":"legalone-mcp","type":"http","url":"https://api.mcp.ai/p_legalone"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

legalone_odata_get legalone_request legalone_metadata legalone_customfield_options legalone_list_litigations legalone_get_litigations legalone_create_litigations legalone_update_litigations legalone_list_lawsuits legalone_get_lawsuits legalone_create_lawsuits legalone_update_lawsuits legalone_list_contacts legalone_get_contacts legalone_create_contacts legalone_update_contacts legalone_list_appointments legalone_get_appointments legalone_create_appointments legalone_update_appointments legalone_list_tasks legalone_get_tasks legalone_create_tasks legalone_update_tasks legalone_list_appointmentstasks legalone_get_appointmentstasks legalone_list_updates legalone_get_updates legalone_create_updates legalone_list_documents legalone_get_documents legalone_list_areas legalone_get_areas legalone_list_servicetypes legalone_get_servicetypes legalone_list_users legalone_get_users legalone_list_customfielddefinitions legalone_get_customfielddefinitions show_version report_bug connect toolkit_info marketplace authenticate

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-legalone-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-legalone-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.