# io.github.theluckystrike/service-agreement (remote · mcp.zovo.one)

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

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

## Components

- remote · `mcp.zovo.one`: 80/100 (this document), [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, [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

- Endpoint: `https://mcp.zovo.one/mcp/service-agreement`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## Trust breakdown

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

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1340 tokens (~134/item across 10 items; 9 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 10 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.

## Install

### How do I install the io.github.theluckystrike/service-agreement MCP server?

io.github.theluckystrike/service-agreement is a hosted endpoint at https://mcp.zovo.one/mcp/service-agreement, 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.

### Claude

```bash
claude mcp add --transport http theluckystrike-service-agreement 'https://mcp.zovo.one/mcp/service-agreement'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-service-agreement": {
      "url": "https://mcp.zovo.one/mcp/service-agreement"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-service-agreement": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/service-agreement"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-service-agreement]
url = "https://mcp.zovo.one/mcp/service-agreement"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-service-agreement": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/service-agreement",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-service-agreement --url 'https://mcp.zovo.one/mcp/service-agreement' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-service-agreement:
    url: "https://mcp.zovo.one/mcp/service-agreement"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-service-agreement": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/service-agreement"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-service-agreement -t streamable-http -u 'https://mcp.zovo.one/mcp/service-agreement'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-service-agreement": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/service-agreement"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-20 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 79, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-17 (score 78)

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` (~55 tokens)

License status

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.

### `license_activate` (~76 tokens)

Activate license

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.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-service-agreement/mcp-service-agreement#diagnostics

## Score history

- 2026-09-20: 80
- 2026-09-19: 79
- 2026-09-18: 79
- 2026-09-17: 78

## 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 hosted endpoint (https://mcp.zovo.one/mcp/service-agreement).

### Is the io.github.theluckystrike/service-agreement MCP server safe to use?

io.github.theluckystrike/service-agreement scores 80 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/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,288 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/service-agreement MCP server require authentication?

Yes. io.github.theluckystrike/service-agreement 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/service-agreement MCP server still maintained?

io.github.theluckystrike/service-agreement 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.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/service-agreement
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/service-agreement
- 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/mcp-service-agreement.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-service-agreement/mcp-service-agreement.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-service-agreement/mcp-service-agreement