Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/lawclause

NPM · @RENETURCIOS/LAWCLAUSE · 2 COMPONENTS

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

72 Trust /100

Last scanned (17 hours ago)

Scores higher than 44% of npm servers

Category Education and Research

Trust breakdown (7 categories)

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
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +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.

  • 18 Nov 26 +1
    • Stability: unverified → 0.07 ▲ functional
  • 17 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 16 Nov 26 55

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/@reneturcios/lawclause@0.1.0

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 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~517 tokens

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 →

Tool Tokens
get_clause ~155

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.

NameTypeReqDescription
as_of––Read the clause as it stood on this date
keystringyesA canonical key, such as gdpr:art-17:para-1
langstring–Which language to prefer, as a two letter code
whole_subtreeboolean–Also return this clause and everything beneath it in reading order, which is what you want for a whole article

No output schema declared.

No examples provided.

get_document ~81

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.

NameTypeReqDescription
as_of––Read the document as it stood on this date
slugstringyesThe document's slug, such as gdpr

No output schema declared.

No examples provided.

list_documents ~62

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

NameTypeReqDescription
as_of––List the documents in force on this date
limitinteger–How many to return
offsetinteger–Skip this many first

No output schema declared.

No examples provided.

search_policies ~219

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.

NameTypeReqDescription
as_of––Read the documents as they stood on this date
include_explanatoryboolean–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
limitinteger–How many clauses to return
querystringyesThe question, in words

No output schema declared.

No examples provided.

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.

npm · @reneturcios/lawclause

# add to Claude Code
claude mcp add cloudcorprecords-lawclause -- npx -y @reneturcios/lawclause mcp
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.