Legal Doc Analyzer

io.github.vpatser1Published by GitHub account vpatser1v1.1.4Updated Oct 27, 2026

Contract analysis, risk assessment, version diffs, compliance checks (GDPR, CCPA, SOC2)

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

Local MCP server for analyzing contracts: risk assessment, version diffs, and compliance checks against GDPR, CCPA and SOC2.

What you can do
  • Analyze contracts and assess their risk
  • Compare document versions to see what changed
  • Run compliance checks against GDPR, CCPA and SOC2
  • Tool list is not published; the free trial allows 3 calls per tool
When to use it
Useful when an assistant needs to review contract text, flag risky clauses, compare two versions of an agreement, or check a document against privacy and security frameworks such as GDPR, CCPA or SOC2.
Requirements
Runs locally over stdio as the npm package legal-doc-analyzer, so a Node.js environment is needed. A LICENSE_KEY environment variable is required for full use; without it the server runs a free trial limited to 3 calls per tool. The key is emailed after purchase.
Before you install
Full functionality is paid: the LICENSE_KEY is issued after purchase, and the free trial is capped at 3 calls per tool. Contract text may be sensitive; the README and instructions are not published, so it is unclear whether documents are sent to an external service. Review before feeding confidential agreements.

Installation

In SourceWeft

  1. Open Legal Doc Analyzer 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.

Tools

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

Version history

1
  1. v1.1.4LatestSep 16, 2026

Score

25% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.