io.github.theluckystrike/service-agreement
MCPB · SERVICE-AGREEMENT.MCPB · 2 COMPONENTS · SCANNED SEP 20
Service agreements for freelancers: scope, deliverables, rate, termination and liability caps.
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 96 of 96 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 31 of 96 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 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1282 tokens (~142/item across 9 items; 9 tools + 0 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 Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
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 · service-agreement.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.
- 17 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.22.0/service-agreement.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 |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
agreement_checklist Check an agreement before you send it ~94
The before-you-send-it checklist for one agreement: every missing field is listed, and terms whose absence cuts one way are flagged neutrally -- as written, what the gap means for both parties -- such as no termination clause or an uncapped liability. Reads only.
| Name | Type | Req | Description |
|---|---|---|---|
| agreement | string | yes | The agreement id, e.g. SA-2026-0003, or the client name when only one agreement has it |
No output schema declared.
No examples provided.
agreement_create Write a service agreement ~506
Write a service agreement between a freelancer and a client before the work starts: the parties, the scope of services, the deliverables, the rate and payment terms, start and end dates, a termination notice period, a liability cap and the governing jurisdiction. Stores the agreement and returns it rendered as clean Markdown with a signature block. Free tier: 3 active agreements; expiring a finished one frees its slot.
| Name | Type | Req | Description |
|---|---|---|---|
| clauses | array | – | Ids of library clauses to include, from clause_library: ip_assignment, confidentiality, late_payment, kill_fee, revision_rounds. The clause library is a Pro feature |
| client | string | yes | Who the work is for, e.g. Brightleaf Studio |
| client_address | string | – | – |
| currency | string | yes | ISO code the rate and cap are in |
| deliverables | array | yes | What the client receives at the end, e.g. ["Five-page site deployed to the client's host", "Handover document"] |
| end_date | string | – | The date the engagement ends, YYYY-MM-DD. Leave unset for an open-ended engagement |
| freelancer | string | yes | Who does the work, e.g. Anna Nowak, or Nowak Design |
| freelancer_address | string | – | – |
| jurisdiction | string | – | The governing law and courts, e.g. England and Wales, or the State of New York |
| liability_cap_cents | integer | – | The most the freelancer can be liable for, in whole cents. Leave unset and liability is uncapped, which the checklist flags |
| note | string | – | – |
| payment_terms | string | yes | When and how it is paid, e.g. Net 14 from invoice date, or 50% on signing and 50% on delivery |
| rate_cents | integer | yes | The rate in whole cents. 8500 is 85.00 |
| rate_unit | string | yes | What the rate buys: an hour, a day, or the whole project |
| scope | string | yes | The services the freelancer provides, e.g. Design and build of a five-page marketing site, with two weeks of post-launch fixes |
| start_date | string | – | The date work begins, YYYY-MM-DD. May be in the future; it is a plan, not a log |
| termination_notice_days | integer | – | Days of written notice either party must give to end the agreement, e.g. 14 |
No output schema declared.
No examples provided.
agreement_get Read one agreement ~89
Read one service agreement in full by SA number or client name: parties, scope, deliverables, rate and payment terms, dates, termination, liability cap, jurisdiction, the clauses it carries, its status and its status history. Reads only.
| Name | Type | Req | Description |
|---|---|---|---|
| agreement | string | yes | The agreement id, e.g. SA-2026-0003, or the client name when only one agreement has it |
No output schema declared.
No examples provided.
agreement_list List agreements ~90
List service agreements newest first: parties, status, rate, dates and the clauses each carries. Filter by status and by client. An agreement is active until it is expired; the free tier holds 3 active agreements.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Only agreements whose client contains this text, case-insensitive |
| status | string | – | Only agreements at this status: draft, sent, signed, expired |
No output schema declared.
No examples provided.
agreement_render Render an agreement for signing ~142
Render a service agreement ready to send and sign: the parties, the services, the deliverables, the payment terms, the term, termination, liability, jurisdiction, any library clauses it carries, and a signature block for both parties. Markdown, or self-contained HTML with print CSS that needs nothing from the network. HTML is a Pro feature. Writes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| agreement | string | yes | The agreement id, e.g. SA-2026-0003, or the client name when only one agreement has it |
| format | string | – | markdown (default) or html. The HTML carries its own styling and references nothing external. HTML is a Pro feature |
No output schema declared.
No examples provided.
agreement_update_status Move an agreement one step ~139
Move one agreement exactly one step: draft, sent, signed, expired, stamping the date and an optional note into its history. A skipped or backwards step is refused and nothing is written. Expiring a finished engagement frees a free-tier slot.
| Name | Type | Req | Description |
|---|---|---|---|
| agreement | string | yes | The agreement id, e.g. SA-2026-0003, or the client name when only one agreement has it |
| date | string | – | The date to stamp the step with, YYYY-MM-DD. Default today |
| note | string | – | – |
| status | string | yes | The next step for this agreement: draft, sent, signed, expired |
No output schema declared.
No examples provided.
clause_library List the built-in clause library ~97
List the built-in clause library: intellectual property assignment, mutual confidentiality, late payment interest, kill fee and revision rounds. Each clause is a title plus a body text. Pass an agreement and, on Pro, every body comes back with that agreement's variables filled in. The free tier lists titles and summaries; the full texts are a Pro feature.
| Name | Type | Req | Description |
|---|---|---|---|
| agreement | string | – | Fill each clause body with this agreement's variables. Pro feature |
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.
What is the io.github.theluckystrike/service-agreement MCP server?
io.github.theluckystrike/service-agreement is an MCP server listed in the public MCP registry as io.github.theluckystrike/service-agreement. Service agreements for freelancers: scope, deliverables, rate, termination and liability caps. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/service-agreement.mcpb).
Is the io.github.theluckystrike/service-agreement MCP server safe to use?
io.github.theluckystrike/service-agreement 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/service-agreement MCP server expose?
io.github.theluckystrike/service-agreement exposes 9 tools: agreement_create, agreement_get, agreement_list, agreement_update_status, clause_library, and 4 more. Their descriptions and schemas cost roughly 1,282 tokens of context every time the server is loaded.
What licence is the io.github.theluckystrike/service-agreement MCP server under?
io.github.theluckystrike/service-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.