io.github.vpatser1/legal-doc-analyzer
NPM · LEGAL-DOC-ANALYZER · SCANNED SEP 24
Contract analysis, risk assessment, version diffs, compliance checks (GDPR, CCPA, SOC2)
Available components
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 39 of 123 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 50 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 465 tokens (~93/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.vpatser1/legal-doc-analyzer MCP server?
io.github.vpatser1/legal-doc-analyzer runs locally as an npm package, launched with npx -y legal-doc-analyzer. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · legal-doc-analyzer
claude mcp add vpatser1-legal-doc-analyzer -- npx -y legal-doc-analyzer
{
"mcpServers": {
"vpatser1-legal-doc-analyzer": {
"command": "npx",
"args": [
"-y",
"legal-doc-analyzer"
]
}
}
} {
"servers": {
"vpatser1-legal-doc-analyzer": {
"command": "npx",
"args": [
"-y",
"legal-doc-analyzer"
]
}
}
} codex mcp add vpatser1-legal-doc-analyzer -- npx -y legal-doc-analyzer
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vpatser1-legal-doc-analyzer": {
"type": "local",
"command": [
"npx",
"-y",
"legal-doc-analyzer"
],
"enabled": true
}
}
} openclaw mcp add vpatser1-legal-doc-analyzer --command npx --arg -y --arg legal-doc-analyzer
mcp_servers:
vpatser1-legal-doc-analyzer:
command: "npx"
args: ["-y", "legal-doc-analyzer"] {
"McpServers": {
"vpatser1-legal-doc-analyzer": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"legal-doc-analyzer"
]
}
}
} assistant mcp add vpatser1-legal-doc-analyzer -t stdio -c npx -a -y legal-doc-analyzer
{
"mcpServers": {
"vpatser1-legal-doc-analyzer": {
"command": "npx",
"args": [
"-y",
"legal-doc-analyzer"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +2
- CVE-2026-82562 no longer affects this package ▲ security
- CVE-2026-82417 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.77 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Analysed npm/legal-doc-analyzer@1.1.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 123 packages
| Packages resolved | 123 |
|---|---|
| Stale | 39 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_contract ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| document_text | string | yes | 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. |
No output schema declared.
No examples provided.
check_compliance ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| document_text | string | yes | The full text of the legal document to check. |
| frameworks | array | – | Compliance frameworks to check against. Defaults to all frameworks if omitted. |
No output schema declared.
No examples provided.
compare_versions ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| labels | object | – | Optional labels for the two versions. |
| new_version | string | yes | The text of the revised / newer version of the document. |
| old_version | string | yes | The text of the original / earlier version of the document. |
No output schema declared.
No examples provided.
find_risks ~107
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).
| Name | Type | Req | Description |
|---|---|---|---|
| document_text | string | yes | The full text of the legal document to assess for risks. |
No output schema declared.
No examples provided.
generate_summary ~59
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.
| Name | Type | Req | Description |
|---|---|---|---|
| document_text | string | yes | The full text of the legal document to summarize. |
No output schema declared.
No examples provided.
What is the io.github.vpatser1/legal-doc-analyzer MCP server?
io.github.vpatser1/legal-doc-analyzer is an MCP server listed in the public MCP registry as io.github.vpatser1/legal-doc-analyzer. Contract analysis, risk assessment, version diffs, compliance checks (GDPR, CCPA, SOC2). This page covers its npm package (legal-doc-analyzer).
Is the io.github.vpatser1/legal-doc-analyzer MCP server safe to use?
io.github.vpatser1/legal-doc-analyzer scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.vpatser1/legal-doc-analyzer MCP server expose?
io.github.vpatser1/legal-doc-analyzer exposes 5 tools: analyze_contract, find_risks, compare_versions, generate_summary, check_compliance. Their descriptions and schemas cost roughly 465 tokens of context every time the server is loaded.
Is the io.github.vpatser1/legal-doc-analyzer MCP server still maintained?
io.github.vpatser1/legal-doc-analyzer is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.vpatser1/legal-doc-analyzer MCP server under?
io.github.vpatser1/legal-doc-analyzer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.