io.github.theluckystrike/glossary-terms-definitions-library
MCPB · CLAUSES.MCPB · 2 COMPONENTS · SCANNED SEP 30
A personal glossary of terms and definitions, assembled into a real Word docx, 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
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 113 of 113 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 113 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 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 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
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
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.
How do I install the io.github.theluckystrike/glossary-terms-definitions-library MCP server?
io.github.theluckystrike/glossary-terms-definitions-library ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · clauses.mcpb
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 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 30 Sept 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/clauses.mcpb@0.22.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 113 packages
| Packages resolved | 113 |
|---|---|
| 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 ~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 ~71
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.
| 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 ~54
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.
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/glossary-terms-definitions-library MCP server?
io.github.theluckystrike/glossary-terms-definitions-library is an MCP server listed in the public MCP registry as io.github.theluckystrike/glossary-terms-definitions-library. A personal glossary of terms and definitions, assembled into a real Word docx, variables filled. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/clauses.mcpb).
Is the io.github.theluckystrike/glossary-terms-definitions-library MCP server safe to use?
io.github.theluckystrike/glossary-terms-definitions-library 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/glossary-terms-definitions-library MCP server expose?
io.github.theluckystrike/glossary-terms-definitions-library 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/glossary-terms-definitions-library MCP server under?
io.github.theluckystrike/glossary-terms-definitions-library declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.