# io.github.theluckystrike/agreement (mcpb · clauses.mcpb)

Reusable agreement and proposal clauses assembled into a real Word docx, variables filled.

- Trust score: 53/100 (low)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- mcpb · `clauses.mcpb`: 53/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-agreement/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-clauses-mc.md), [page](https://verifymcp.io/servers/theluckystrike-agreement/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-clauses-mc)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/clauses.mcpb`
- Version: `0.21.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 13 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 85/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).
  - Tool/resource definitions use about 1272 tokens (~97/item across 13 items; 12 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.

## Install

- Download bundle: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.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-19 (score 53, +1)

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

### 2026-09-17 (score 52, +1)

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

### 2026-09-15 (score 51, +1)

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

### 2026-09-14 (score 50, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-09-07 (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` (~61 tokens)

Read one clause

Return a clause in full by id or by title, with its variables and, in Pro, its revision count.

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` (~41 tokens)

Delete a clause

Remove a clause from the library. A deleted starter clause is not re-seeded on the next call.

Input parameters:

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

### `clause_list` (~29 tokens)

List clauses

List every clause, newest categories first, optionally narrowed to one category.

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` (~141 tokens)

Import clauses

Call this tool to bulk-load clauses into the library from a markdown or JSON file. Returns how many clauses were added, replaced, skipped and blocked by the free clause cap, plus the new library total.

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` (~104 tokens)

Export clauses

Call this tool to write the whole clause library out to one file. Returns the destination path, the format used and how many clauses were written.

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` (~292 tokens)

Assemble a contract

Call this tool to build a contract or proposal document from library clauses. Returns the path written, the clauses used in document order, which variables were filled, and the facts still missing as bracketed prompts.

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` (~46 tokens)

List the variables a selection needs

Given a set of clauses, list every {{variable}} they use and which clause uses it, so nothing is missed before assembling.

Input parameters:

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

### `license_status` (~23 tokens)

License status

Show whether this server runs in free or Pro mode and where to upgrade.

### `license_activate` (~42 tokens)

Activate license

Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.

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-agreement/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-clauses-mc#diagnostics

## Score history

- 2026-09-20: 53
- 2026-09-19: 53
- 2026-09-18: 52
- 2026-09-17: 52
- 2026-09-16: 51
- 2026-09-15: 51
- 2026-09-14: 50
- 2026-09-13: 47
- 2026-09-12: 47
- 2026-09-11: 47
- 2026-09-10: 47
- 2026-09-09: 47
- 2026-09-08: 47
- 2026-09-07: 47

## Common questions

### What is the io.github.theluckystrike/agreement MCP server?

io.github.theluckystrike/agreement is an MCP server listed in the public MCP registry as io.github.theluckystrike/agreement. Reusable agreement and proposal clauses assembled into a real Word docx, variables filled. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/clauses.mcpb).

### Is the io.github.theluckystrike/agreement MCP server safe to use?

io.github.theluckystrike/agreement scores 53 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/agreement MCP server expose?

io.github.theluckystrike/agreement exposes 12 tools: clause_add, clause_get, clause_update, clause_delete, clause_list, and 7 more. Their descriptions and schemas cost roughly 1,254 tokens of context every time the server is loaded.

### What licence is the io.github.theluckystrike/agreement MCP server under?

io.github.theluckystrike/agreement 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-agreement/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-clauses-mc.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-agreement/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-clauses-mc.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-agreement/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-clauses-mc