# io.github.theluckystrike/service-agreement (mcpb · service-agreement.mcpb)

Service agreements for freelancers: scope, deliverables, rate, termination and liability caps.

- Trust score: 47/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.zovo.one`: 80/100, [markdown](https://verifymcp.io/servers/theluckystrike-service-agreement/mcp-service-agreement.md), [page](https://verifymcp.io/servers/theluckystrike-service-agreement/mcp-service-agreement)
- mcpb · `service-agreement.mcpb`: 47/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-service-agreement/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-service-ag.md), [page](https://verifymcp.io/servers/theluckystrike-service-agreement/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-service-ag)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/service-agreement.mcpb`
- Version: `0.22.0`
- Transport: `stdio`

## Trust breakdown

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. 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.

- **Supply Chain Security**: 23/100
  - Malware scan not yet available for this package.
  - Known CVEs were checked across the 96 of 96 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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.

**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.

## Install

- Download bundle: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/service-agreement.mcpb`

## 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-17 (score 47)

First indexed and scored.

## MCP tools (9)

### `agreement_create` (~506 tokens)

Write a service agreement

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.

Input parameters:

- `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, required): Who the work is for, e.g. Brightleaf Studio
- `client_address` (string)
- `currency` (string, required): ISO code the rate and cap are in
- `deliverables` (array, required): 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, required): 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, required): When and how it is paid, e.g. Net 14 from invoice date, or 50% on signing and 50% on delivery
- `rate_cents` (integer, required): The rate in whole cents. 8500 is 85.00
- `rate_unit` (string, required): What the rate buys: an hour, a day, or the whole project
- `scope` (string, required): 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

### `agreement_get` (~89 tokens)

Read one agreement

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.

Input parameters:

- `agreement` (string, required): The agreement id, e.g. SA-2026-0003, or the client name when only one agreement has it

### `agreement_list` (~90 tokens)

List agreements

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.

Input parameters:

- `client` (string): Only agreements whose client contains this text, case-insensitive
- `status` (string): Only agreements at this status: draft, sent, signed, expired

### `agreement_update_status` (~139 tokens)

Move an agreement one step

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.

Input parameters:

- `agreement` (string, required): 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, required): The next step for this agreement: draft, sent, signed, expired

### `clause_library` (~97 tokens)

List the built-in clause library

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.

Input parameters:

- `agreement` (string): Fill each clause body with this agreement's variables. Pro feature

### `agreement_render` (~142 tokens)

Render an agreement for signing

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.

Input parameters:

- `agreement` (string, required): 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

### `agreement_checklist` (~94 tokens)

Check an agreement before you send it

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.

Input parameters:

- `agreement` (string, required): The agreement id, e.g. SA-2026-0003, or the client name when only one agreement has it

### `license_status` (~54 tokens)

License status

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.

### `license_activate` (~71 tokens)

Activate license

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.

Input parameters:

- `key` (string, required): License key from the checkout confirmation page

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/theluckystrike-service-agreement/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-service-ag#diagnostics

## Score history

- 2026-09-20: 47
- 2026-09-19: 47
- 2026-09-18: 47
- 2026-09-17: 47

## Common questions

### 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.

## Links

- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/service-agreement
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-service-agreement/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-service-ag.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-service-agreement/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-service-ag.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-service-agreement/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-service-ag