io.github.theluckystrike/contract-clause-library-proposal-template-docx
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
A personal library of reusable contract and proposal clauses, assembled into a real Word .docx.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1492 tokens (~106/item across 14 items; 12 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 13 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
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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-contract-clause-library-proposal- 'https://mcp.zovo.one/mcp/clauses'
{
"mcpServers": {
"theluckystrike-contract-clause-library-proposal-": {
"url": "https://mcp.zovo.one/mcp/clauses"
}
}
} {
"servers": {
"theluckystrike-contract-clause-library-proposal-": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/clauses"
}
}
} [mcp_servers.theluckystrike-contract-clause-library-proposal-] url = "https://mcp.zovo.one/mcp/clauses"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-contract-clause-library-proposal-": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/clauses",
"enabled": true
}
}
} openclaw mcp add theluckystrike-contract-clause-library-proposal- --url 'https://mcp.zovo.one/mcp/clauses' --transport streamable-http
mcp_servers:
theluckystrike-contract-clause-library-proposal-:
url: "https://mcp.zovo.one/mcp/clauses" {
"McpServers": {
"theluckystrike-contract-clause-library-proposal-": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/clauses"
}
}
} assistant mcp add theluckystrike-contract-clause-library-proposal- -t streamable-http -u 'https://mcp.zovo.one/mcp/clauses'
{
"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.
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 Sept 26 +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.
- 18 Sept 26 +56
- Authorization: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.30 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 17 Sept 26 −55
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.23 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Server version: 0.21.0 → 0.22.0 functional
- 16 Sept 26 +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.
- 13 Sept 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.
- 11 Sept 26 +1
- Tool “license_activate” rewrote its description, which is the text the model reads security
- Schema quality: fail → pass ▲ functional
- New prompt “upgrade_to_pro” functional
- New resource “pricing” functional
- 10 Sept 26 +1
- Tool “license_activate” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “license_activate” reworded the description of “key” cosmetic
- 9 Sept 26 +40
- Transport: unverified → pass ▲ security
- 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. security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 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 functional
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 20 Sept 2026 · Probed https://mcp.zovo.one/mcp/clauses
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/clauses | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/clauses | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/clauses |
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 →
clause_add Add a clause ~257
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | 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 | yes | 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 | yes | Clause heading, for example 'Late Payment' |
| variables | array | – | Declared variable names. Anything {{...}} in the body is detected anyway |
No output schema declared.
No examples provided.
clause_delete Delete a clause ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Clause id or exact title |
No output schema declared.
No examples provided.
clause_export Export clauses ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | 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 | yes | Destination file path. The clauses are written in assembly order, categories first |
No output schema declared.
No examples provided.
clause_get Read one clause ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Clause id, for example late-fees |
| title | string | – | Clause title; a partial title matches too |
No output schema declared.
No examples provided.
clause_import Import clauses ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| overwrite | boolean | – | Replace clauses whose title already exists instead of skipping them |
| path | string | yes | 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… |
No output schema declared.
No examples provided.
clause_list List clauses ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
No output schema declared.
No examples provided.
clause_search Search clauses ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| jurisdiction | string | – | Exact jurisdiction match. Free |
| query | string | yes | 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 |
No output schema declared.
No examples provided.
clause_update Update a clause ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| category | string | – | – |
| id | string | yes | Clause id or exact title |
| jurisdiction | string | – | – |
| language | string | – | – |
| tags | array | – | – |
| title | string | – | – |
| variables | array | – | – |
No output schema declared.
No examples provided.
contract_assemble Assemble a contract ~295
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
No output schema declared.
No examples provided.
license_activate Activate license ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
variables_list List the variables a selection needs ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| clause_ids | array | yes | Clause ids or titles |
No output schema declared.
No examples provided.
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.