# io.github.CloudCorpRecords/lawclause (npm · @reneturcios/lawclause)

Search and cite privacy law clauses: GDPR and UAE PDPL texts, documents and versions.

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

## Components

- npm · `@reneturcios/lawclause`: 72/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-lawclause/reneturcios-lawclause.md), [page](https://verifymcp.io/servers/cloudcorprecords-lawclause/reneturcios-lawclause)
- oci · `ghcr.io/cloudcorprecords/lawclause`: 43/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-lawclause/ghcr-io-cloudcorprecords-lawclause.md), [page](https://verifymcp.io/servers/cloudcorprecords-lawclause/ghcr-io-cloudcorprecords-lawclause)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/lawclause`
- Version: `0.1.0`
- 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-11-21.

- **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.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 517 tokens (~129/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.CloudCorpRecords/lawclause MCP server?

io.github.CloudCorpRecords/lawclause runs locally as an npm package, launched with npx -y @reneturcios/lawclause mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-lawclause -- npx -y @reneturcios/lawclause mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-lawclause": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/lawclause",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-lawclause": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/lawclause",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-lawclause -- npx -y @reneturcios/lawclause mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-lawclause": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/lawclause",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-lawclause --command npx --arg -y --arg @reneturcios/lawclause --arg mcp
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-lawclause:
    command: "npx"
    args: ["-y", "@reneturcios/lawclause", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-lawclause": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/lawclause",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-lawclause -t stdio -c npx -a -y @reneturcios/lawclause mcp
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-lawclause": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/lawclause",
        "mcp"
      ]
    }
  }
}
```

## 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-11-20 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 71, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-11-17 (score 70, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-16 (score 55)

First indexed and scored.

## MCP tools (4)

### `search_policies` (~219 tokens)

Search the law

Search the privacy law this community version holds.

Call this before writing or changing code that collects, stores, logs, shares or deletes
personal data, and before answering a question about what the law requires. What comes back
is the clause itself, word for word, with the key, document and version to cite it by.

Questions asked here are kept 30 days, with nothing about who asked.

Input parameters:

- `as_of`: Read the documents as they stood on this date
- `include_explanatory` (boolean): Include text that explains without obliging, such as a GDPR recital
- `lang`: The language of the question, en or ar. Leave it out to have it read from the letters the question is written in
- `laws`: Only these of the laws this organisation has selected, by slug, such as gdpr or uae-pdpl. Leave it out to search all of them
- `limit` (integer): How many clauses to return
- `query` (string, required): The question, in words

### `get_clause` (~155 tokens)

Read one clause

Read one clause by its key, with where it sits and what sits beneath it.

Use it when a search result points at another clause, or when you need the whole
of an article rather than the part that matched. The call is recorded, with the
key that was read rather than a question.

Input parameters:

- `as_of`: Read the clause as it stood on this date
- `key` (string, required): A canonical key, such as gdpr:art-17:para-1
- `lang` (string): Which language to prefer, as a two letter code
- `whole_subtree` (boolean): Also return this clause and everything beneath it in reading order, which is what you want for a whole article

### `list_documents` (~62 tokens)

List what can be cited

List the laws this community version can cite, and which version of each is in force.

Input parameters:

- `as_of`: List the documents in force on this date
- `limit` (integer): How many to return
- `offset` (integer): Skip this many first

### `get_document` (~81 tokens)

Read one document's outline

Read one document and its top level structure, without the text.

The outline is where to find a clause key when you know roughly where to look.
Read the words with get_clause. The call is recorded.

Input parameters:

- `as_of`: Read the document as it stood on this date
- `slug` (string, required): The document's slug, such as gdpr

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-lawclause/reneturcios-lawclause#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 72
- 2026-11-19: 71
- 2026-11-18: 71
- 2026-11-17: 70
- 2026-11-16: 55

## Common questions

### What is the io.github.CloudCorpRecords/lawclause MCP server?

io.github.CloudCorpRecords/lawclause is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/lawclause. Search and cite privacy law clauses: GDPR and UAE PDPL texts, documents and versions. This page covers its npm package (@reneturcios/lawclause).

### Is the io.github.CloudCorpRecords/lawclause MCP server safe to use?

io.github.CloudCorpRecords/lawclause scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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.CloudCorpRecords/lawclause MCP server expose?

io.github.CloudCorpRecords/lawclause exposes 4 tools: search_policies, get_clause, list_documents, get_document. Their descriptions and schemas cost roughly 517 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/lawclause MCP server still maintained?

io.github.CloudCorpRecords/lawclause is still listed as active in the MCP registry. We last reached this channel on 21 November 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.CloudCorpRecords/lawclause MCP server under?

io.github.CloudCorpRecords/lawclause declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.CloudCorpRecords/lawclause MCP server?

VerifyMCP ran 16 checks on io.github.CloudCorpRecords/lawclause, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/lawclause
- Socket report: https://socket.dev/npm/package/@reneturcios/lawclause
- Repository: https://github.com/CloudCorpRecords/lawclause
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-lawclause/reneturcios-lawclause.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-lawclause/reneturcios-lawclause/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-lawclause/reneturcios-lawclause.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-lawclause/reneturcios-lawclause
