# io.github.theluckystrike/contract-clause-library-proposal-template-docx (mcpb · clauses.mcpb)

A personal library of reusable contract and proposal clauses, assembled into a real Word .docx.

- Trust score: 47/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.zovo.one`: 82/100, [markdown](https://verifymcp.io/servers/theluckystrike-contract-clause-library-proposal-template-docx/mcp-clauses.md), [page](https://verifymcp.io/servers/theluckystrike-contract-clause-library-proposal-template-docx/mcp-clauses)
- mcpb · `clauses.mcpb`: 47/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-contract-clause-library-proposal-template-docx/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-clauses-mc.md), [page](https://verifymcp.io/servers/theluckystrike-contract-clause-library-proposal-template-docx/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-clauses-mc)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/clauses.mcpb`
- Version: `0.22.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-09-20.

- **Supply Chain Security**: 23/100
  - Malware scan not yet available for this package.
  - Known CVEs were checked across the 117 of 117 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 44 of 117 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 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1436 tokens (~110/item across 13 items; 12 tools + 1 resources), over budget; trim descriptions and params.
  - 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**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 74% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "clause_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 13 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.

**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

- Download bundle: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/clauses.mcpb`

## 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-09-17 (score 47)

First indexed and scored.

## MCP tools (12)

### `clause_add` (~257 tokens)

Add a clause

Save a reusable contract or proposal clause to the library. Returns the stored clause id, title, category, tags and the variables detected in its body, plus how many clauses of your own the library now holds.

Input parameters:

- `body` (string, required): The clause text. Use {{variable}} placeholders for the facts that change per client, for example {{client}}, {{fee}} or {{late_fee_percent}}; contract_assemble fills them at assembly time. Free tier:…
- `category` (string, required): Grouping. The known ones, in assembly order, are parties, scope, payment, expenses, ip, confidentiality, data, term, liability, warranty, disputes, general -- reuse one of these; any other name is ac…
- `jurisdiction` (string): Where the clause is meant to apply, for example 'PL' or 'England and Wales'
- `language` (string): ISO language code, default en
- `tags` (array)
- `title` (string, required): Clause heading, for example 'Late Payment'
- `variables` (array): Declared variable names. Anything {{...}} in the body is detected anyway

### `clause_get` (~80 tokens)

Read one clause

Return one clause in full by id or title: body, category, tags, jurisdiction, variables and the revision count, which stays 0 on free. A partial title matching several is refused with the candidates.

Input parameters:

- `id` (string): Clause id, for example late-fees
- `title` (string): Clause title; a partial title matches too

### `clause_update` (~106 tokens)

Update a clause

Change the text, category, tags, variables or jurisdiction of a clause. In Pro the previous text is kept as a version; in the free tier the change is applied without history.

Input parameters:

- `body` (string)
- `category` (string)
- `id` (string, required): Clause id or exact title
- `jurisdiction` (string)
- `language` (string)
- `tags` (array)
- `title` (string)
- `variables` (array)

### `clause_delete` (~62 tokens)

Delete a clause

Delete one clause by id or exact title and report how many are left. There is no undo, and a deleted starter clause is not re-seeded. Use clause_update to change one you want to keep.

Input parameters:

- `id` (string, required): Clause id or exact title

### `clause_list` (~56 tokens)

List clauses

List the library as id, title, category, tags and variables, in contract order by category then title, which is the order contract_assemble uses. Narrow with category; use clause_search for words.

Input parameters:

- `category` (string)

### `clause_search` (~112 tokens)

Search clauses

Ranked search over clause titles, tags, categories and bodies. Title and tag matches outrank body matches. Jurisdiction filtering is free; the tag filter is Pro and is skipped rather than refusing the search.

Input parameters:

- `category` (string)
- `jurisdiction` (string): Exact jurisdiction match. Free
- `query` (string, required): Words to look for, for example 'late payment interest'
- `tags` (array): Pro: every tag listed must be present. On free the search still runs, without this filter

### `clause_import` (~145 tokens)

Import clauses

Call this tool to load clauses from a .md or .json file, reporting added, replaced, skipped and capped counts. A duplicate title is skipped unless overwrite. json is Pro. Free: 10 of your own.

Input parameters:

- `overwrite` (boolean): Replace clauses whose title already exists instead of skipping them
- `path` (string, required): Path to a .md or .json file. Markdown form: '## Title', then optional 'category:' / 'tags:' / 'variables:' lines, a blank line, then the body. JSON form: an array of clauses. JSON import is a Pro fea…

### `clause_export` (~119 tokens)

Export clauses

Call this tool to write the whole library to one file and return the path, format and count. It is written in contract order, so it re-imports the same way. markdown is free; json is Pro.

Input parameters:

- `format` (string, required): json (a Pro feature) or markdown (works in the free tier)
- `overwrite` (boolean): Replace the destination if a file is already there. Without it an existing file is never touched
- `path` (string, required): Destination file path. The clauses are written in assembly order, categories first

### `contract_assemble` (~295 tokens)

Assemble a contract

Call this tool to build a contract from library clauses as .docx or markdown. A variable you omit stays as a bracketed prompt, never invented. clause_ids order is document order. Free: 8 clauses.

Input parameters:

- `categories` (array): Instead of ids: every clause in these categories, ordered by category. Free tier: up to 8 clauses per document
- `clause_ids` (array): Clause ids in the order they should appear; this is the document order. Free tier: up to 8 clauses per document
- `client` (string): Client name; also fills the {{client}} variable
- `format` (string): docx (default) or markdown; the document opens with the not-legal-advice line either way
- `out_path` (string): Where to write the file. Default: the server data directory, under a name built from the client and the title
- `overwrite` (boolean): Replace out_path if a file is already there. Without it an existing file is never touched
- `title` (string, required): Document title, for example 'Service Agreement - Beta Corp'
- `values` (object): Values for the {{variables}} in the chosen clauses, for example {"fee":"4500","late_fee_percent":"2"}. Any variable you leave out stays in the document as a bracketed prompt such as [late fee percent…

### `variables_list` (~61 tokens)

List the variables a selection needs

List every {{variable}} the clauses you name use, and which clause uses each, so the facts are gathered before contract_assemble leaves bracketed prompts. Reads only; a title matching several is refused.

Input parameters:

- `clause_ids` (array, required): Clause ids or titles

### `license_status` (~54 tokens)

License status

Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.

### `license_activate` (~71 tokens)

Activate license

Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.

Input parameters:

- `key` (string, required): License key from the checkout confirmation page

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/theluckystrike-contract-clause-library-proposal-template-docx/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-clauses-mc#diagnostics

## Score history

- 2026-09-20: 47
- 2026-09-19: 47
- 2026-09-18: 47
- 2026-09-17: 47

## Common questions

### What is the io.github.theluckystrike/contract-clause-library-proposal-t… MCP server?

io.github.theluckystrike/contract-clause-library-proposal-t… is an MCP server listed in the public MCP registry as io.github.theluckystrike/contract-clause-library-proposal-t…. A personal library of reusable contract and proposal clauses, assembled into a real Word .docx. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/clauses.mcpb).

### Is the io.github.theluckystrike/contract-clause-library-proposal-t… MCP server safe to use?

io.github.theluckystrike/contract-clause-library-proposal-t… scores 47 out of 100 on VerifyMCP. 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.theluckystrike/contract-clause-library-proposal-t… MCP server expose?

io.github.theluckystrike/contract-clause-library-proposal-t… exposes 12 tools: clause_add, clause_get, clause_update, clause_delete, clause_list, and 7 more. Their descriptions and schemas cost roughly 1,418 tokens of context every time the server is loaded.

### What licence is the io.github.theluckystrike/contract-clause-library-proposal-t… MCP server under?

io.github.theluckystrike/contract-clause-library-proposal-t… declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/clauses
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-contract-clause-library-proposal-template-docx/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-clauses-mc.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-contract-clause-library-proposal-template-docx/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-clauses-mc.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-contract-clause-library-proposal-template-docx/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-clauses-mc