Legal Mcp Server

io.github.TheNextGenNexusPublished by GitHub account TheNextGenNexusv1.0.1Updated Oct 24, 2026

Search court records, patents, and trademarks for legal research

VerifiedSTDIODesktop onlyWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

A local MCP server that lets an assistant search US court records, patents and trademarks for legal research, forwarding queries to an Apify endpoint.

What you can do
Search US court records by name, case number or jurisdiction, and search patent databases for inventions and IP, and look up trademark registrations. Each tool call is forwarded from the local stdio bridge to the nexgendata Apify endpoint, which returns the results.
When to use it
Useful when you want an assistant to gather preliminary legal research on litigation, patents or trademarks without leaving the chat, for example checking whether a name is already trademarked or finding related court cases.
Requirements
Runs as a local process via npx or a global npm install, so Node.js and npm are needed. It is configured in a desktop client such as Claude Desktop or Cline. The APIFY_TOKEN environment variable is listed as required in the manifest, though the README describes it as optional and says the public endpoint is used without it, rate-limited. Network access to Apify is required.
Before you install
Queries are sent to a third-party Apify endpoint, so search terms leave your machine. APIFY_TOKEN is an Apify API credential; keep it out of shared configs. Results come from an external scraping service and may be incomplete or out of date, so they are not legal advice.

Installation

In SourceWeft

  1. Open Legal Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Legal Research MCP Server

Search court records, patents, and trademarks for legal research — powered by nexgendata on Apify.

Quick Start

Using npx (recommended)

bash
npx @nexgendata/legal-mcp-server

Install globally

bash
npm install -g @nexgendata/legal-mcp-server

Configure with Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

json
{      "mcpServers": {            "legal-mcp-server": {                  "command": "npx",                  "args": [                        "-y",                        "@nexgendata/legal-mcp-server"                  ],                  "env": {                        "APIFY_TOKEN": "your-apify-token-optional"                  }            }      }}

Configure with Cline

Add the same configuration to your Cline MCP settings.

Available Tools

ToolDescription
search_court_recordsSearch US court records by name, case number, or jurisdiction
search_patentsSearch patent databases for inventions and IP
search_trademarksSearch trademark registrations

Environment Variables

VariableRequiredDescription
APIFY_TOKENNoYour Apify API token for authenticated access. Without it, the server uses the public endpoint (rate-limited).

How It Works

This MCP server acts as a local stdio bridge to the nexgendata Apify MCP endpoint. When you call a tool, it forwards the request to Apify and returns the results.

Links

License

MIT

Source: servers/legal-mcp-server/README.md at commit 26dc208

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.