# io.github.vpatser1/legal-doc-analyzer (npm · legal-doc-analyzer)

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

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-08

## Components

- npm · `legal-doc-analyzer`: 64/100 (this document), [markdown](https://verifymcp.io/servers/vpatser1-legal-doc-analyzer/legal-doc-analyzer.md), [page](https://verifymcp.io/servers/vpatser1-legal-doc-analyzer/legal-doc-analyzer)

## Channel facts

- Registry: `npm`
- Package: `legal-doc-analyzer`
- Version: `1.1.4`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-08.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 36 of 123 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 465 tokens (~93/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add vpatser1-legal-doc-analyzer -- npx -y legal-doc-analyzer
```

### Codex

```bash
codex mcp add vpatser1-legal-doc-analyzer -- npx -y legal-doc-analyzer
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vpatser1-legal-doc-analyzer": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "legal-doc-analyzer"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vpatser1-legal-doc-analyzer --command npx --arg -y --arg legal-doc-analyzer
```

### Hermes

```yaml
mcp_servers:
  vpatser1-legal-doc-analyzer:
    command: "npx"
    args: ["-y", "legal-doc-analyzer"]
```

### Other

```json
{
  "mcpServers": {
    "vpatser1-legal-doc-analyzer": {
      "command": "npx",
      "args": [
        "-y",
        "legal-doc-analyzer"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-08 (score 64, +4)

- [security improvement] Known CVEs: partial → pass
- [functional] Dependency health: partial → 0.85

### 2026-08-04 (score 60)

First indexed and scored.

## MCP tools (5)

### `analyze_contract` (~112 tokens)

Analyzes a contract or legal document. Identifies key parties, contract type (NDA, SaaS, employment, etc.), important dates (effective, termination, renewal), key obligations per party, liability clauses and limits, termination conditions, and governing law/jurisdiction. Returns a structured summary.

Input parameters:

- `document_text` (string, required): The full text of the contract or legal document to analyze.
- `document_type` (string): Type of document. If omitted, the type is auto-detected from the content.

### `find_risks` (~107 tokens)

Flags risks in a legal document: one-sided clauses, unlimited liability exposure, auto-renewal traps, broad non-compete clauses, vague/ambiguous language, missing standard protections (limitation of liability, indemnification caps), and IP assignment concerns. Returns flagged risks with severity ratings, excerpts, recommendations, and a risk score from 0 (minimal) to 100 (critical).

Input parameters:

- `document_text` (string, required): The full text of the legal document to assess for risks.

### `compare_versions` (~100 tokens)

Compares two versions of a legal document. Identifies all changes (added, removed, modified clauses), highlights materially significant changes, flags changes that increase risk, and provides a side-by-side diff summary.

Input parameters:

- `labels` (object): Optional labels for the two versions.
- `new_version` (string, required): The text of the revised / newer version of the document.
- `old_version` (string, required): The text of the original / earlier version of the document.

### `generate_summary` (~59 tokens)

Generates a plain-English summary of a legal document readable by non-lawyers. Includes a key terms table, action items / obligations timeline, and a one-page executive brief.

Input parameters:

- `document_text` (string, required): The full text of the legal document to summarize.

### `check_compliance` (~87 tokens)

Checks a legal document against compliance frameworks (GDPR, CCPA, SOC2, HIPAA). Checks for required clauses, identifies missing provisions, suggests additional language needed, and returns a compliance score per framework.

Input parameters:

- `document_text` (string, required): The full text of the legal document to check.
- `frameworks` (array): Compliance frameworks to check against. Defaults to all frameworks if omitted.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/vpatser1-legal-doc-analyzer/legal-doc-analyzer#diagnostics

## Score history

- 2026-08-08: 64
- 2026-08-07: 60
- 2026-08-06: 60
- 2026-08-05: 60
- 2026-08-04: 60

## Links

- npm package: https://www.npmjs.com/package/legal-doc-analyzer
- Socket report: https://socket.dev/npm/package/legal-doc-analyzer
- Website: https://aivp-mcp.vercel.app/
- Changelog RSS feed: https://verifymcp.io/servers/vpatser1-legal-doc-analyzer/legal-doc-analyzer.xml
- Changelog JSON feed: https://verifymcp.io/servers/vpatser1-legal-doc-analyzer/legal-doc-analyzer.json
- HTML version of this page: https://verifymcp.io/servers/vpatser1-legal-doc-analyzer/legal-doc-analyzer