# io.github.theluckystrike/contract-clause-library-proposal-template-docx (remote · mcp.zovo.one)

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

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.zovo.one`: 82/100 (this document), [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, [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

- Endpoint: `https://mcp.zovo.one/mcp/clauses`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **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 1492 tokens (~106/item across 14 items; 12 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 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

### How do I install the io.github.theluckystrike/contract-clause-library-proposal-t… MCP server?

io.github.theluckystrike/contract-clause-library-proposal-t… is a hosted endpoint at https://mcp.zovo.one/mcp/clauses, so there is nothing to install locally. 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 --transport http theluckystrike-contract-clause-library-proposal- 'https://mcp.zovo.one/mcp/clauses'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-contract-clause-library-proposal-": {
      "url": "https://mcp.zovo.one/mcp/clauses"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-contract-clause-library-proposal-": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/clauses"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-contract-clause-library-proposal-]
url = "https://mcp.zovo.one/mcp/clauses"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-contract-clause-library-proposal-": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/clauses",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-contract-clause-library-proposal- --url 'https://mcp.zovo.one/mcp/clauses' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-contract-clause-library-proposal-:
    url: "https://mcp.zovo.one/mcp/clauses"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-contract-clause-library-proposal-": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/clauses"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-contract-clause-library-proposal- -t streamable-http -u 'https://mcp.zovo.one/mcp/clauses'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-contract-clause-library-proposal-": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/clauses"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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

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

### 2026-09-18 (score 81, +56)

- [security regression] Authorization: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: unverified → pass
- [functional improvement] Endpoint reachability: behind authorisation → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Stability: unverified → 0.30
- [functional improvement] MCP protocol: unverified → pass

### 2026-09-17 (score 25, −55)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Stability: 0.23 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security regression] Authorization: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional] Server version: 0.21.0 → 0.22.0

### 2026-09-16 (score 80, +1)

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

### 2026-09-13 (score 79, +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-09-11 (score 78, +1)

- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: fail → pass
- [functional] New prompt “upgrade_to_pro”
- [functional] New resource “pricing”

### 2026-09-10 (score 77, +1)

- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “license_activate” reworded the description of “key”

### 2026-09-09 (score 76, +40)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 74
- [functional] First check of Destructive annotations: 0
- [functional] First check of Schema quality: good

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

License status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

### `license_activate` (~76 tokens)

Activate license

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-contract-clause-library-proposal-template-docx/mcp-clauses#diagnostics

## Score history

- 2026-09-20: 82
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 25
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 79
- 2026-09-12: 78
- 2026-09-11: 78
- 2026-09-10: 77
- 2026-09-09: 76
- 2026-09-08: 36
- 2026-09-07: 36
- 2026-09-06: 36
- 2026-09-05: 36
- 2026-09-04: 36
- 2026-09-03: 36

## 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 hosted endpoint (https://mcp.zovo.one/mcp/clauses).

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

io.github.theluckystrike/contract-clause-library-proposal-t… scores 82 out of 100 on VerifyMCP. 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,424 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/contract-clause-library-proposal-t… MCP server require authentication?

Yes. io.github.theluckystrike/contract-clause-library-proposal-t… asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.theluckystrike/contract-clause-library-proposal-t… MCP server still maintained?

io.github.theluckystrike/contract-clause-library-proposal-t… is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/clauses
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/clauses
- 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/mcp-clauses.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-contract-clause-library-proposal-template-docx/mcp-clauses.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-contract-clause-library-proposal-template-docx/mcp-clauses