io.github.theluckystrike/service-agreement
REMOTE · MCP.ZOVO.ONE · 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 against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 10 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
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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-service-agreement 'https://mcp.zovo.one/mcp/service-agreement'
{
"mcpServers": {
"theluckystrike-service-agreement": {
"url": "https://mcp.zovo.one/mcp/service-agreement"
}
}
} {
"servers": {
"theluckystrike-service-agreement": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/service-agreement"
}
}
} [mcp_servers.theluckystrike-service-agreement] url = "https://mcp.zovo.one/mcp/service-agreement"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-service-agreement": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/service-agreement",
"enabled": true
}
}
} openclaw mcp add theluckystrike-service-agreement --url 'https://mcp.zovo.one/mcp/service-agreement' --transport streamable-http
mcp_servers:
theluckystrike-service-agreement:
url: "https://mcp.zovo.one/mcp/service-agreement" {
"McpServers": {
"theluckystrike-service-agreement": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/service-agreement"
}
}
} assistant mcp add theluckystrike-service-agreement -t streamable-http -u 'https://mcp.zovo.one/mcp/service-agreement'
{
"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.
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.
- 20 Sept 26 +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.
- 18 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 78
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 · Probed https://mcp.zovo.one/mcp/service-agreement
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/service-agreement | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/service-agreement | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/service-agreement |
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 ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
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.
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 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.