io.github.theluckystrike/terms
MCPB · CLAUSES.MCPB · SCANNED SEP 20
Reusable contract terms and clauses assembled into a Word docx with variables filled.
Available components
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 Security23
- Malware scan not yet available for this package.Unverified
- Known CVEs were checked across the 117 of 117 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 44 of 117 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 1272 tokens (~97/item across 13 items; 12 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 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
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
mcpb · clauses.mcpb
Download bundleEvery 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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 7 Sept 26 47
First indexed and scored.
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 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/clauses.mcpb@0.21.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
Background: How many MCP packages publish verified provenance →
Dependencies 117 packages
| Packages resolved | 117 |
|---|---|
| Stale | 44 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~41
Remove a clause from the library. A deleted starter clause is not re-seeded on the next call.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Clause id or exact title |
No output schema declared.
No examples provided.
clause_export Export clauses ~104
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.
| 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 ~61
Return a clause in full by id or by title, with its variables and, in Pro, its revision count.
| 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 ~141
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.
| 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 ~29
List every clause, newest categories first, optionally narrowed to one category.
| 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 ~292
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.
| 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 ~42
Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~23
Show whether this server runs in free or Pro mode and where to upgrade.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
variables_list List the variables a selection needs ~46
Given a set of clauses, list every {{variable}} they use and which clause uses it, so nothing is missed before assembling.
| 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/terms MCP server?
io.github.theluckystrike/terms is an MCP server listed in the public MCP registry as io.github.theluckystrike/terms. Reusable contract terms and clauses assembled into a Word docx with 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/terms MCP server safe to use?
io.github.theluckystrike/terms 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/terms MCP server expose?
io.github.theluckystrike/terms 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/terms MCP server under?
io.github.theluckystrike/terms declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.