McpStamp Service Agreement

io.github.theluckystrikePublished by GitHub account theluckystrikev0.23.0Updated Nov 3, 2026

Freelance service agreements: scope, deliverables, rate, termination, liability cap, clauses.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

McpStamp Service Agreement's hosted MCP server (mcp.zovo.one); no sign-in required; Streamable HTTP; 9 tools.

No AI overview yet: these facts come from the registry entry and the server itself.

Endpoint
mcp.zovo.one
Last checked

Installation

In SourceWeft

  1. Open McpStamp Service Agreement in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.theluckystrike%2Fservice-agreement/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

mcp-service-agreement

[theluckystrike/mcp-service-agreement MCP server]

In the official MCP Registry (io.github.theluckystrike/service-agreement). An mcp service agreement writer for freelancers who are about to start client work and do not want to copy a rotting template off the internet again. Give it 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, and it stores the agreement and renders clean Markdown, or print-ready HTML, with a signature block for both sides. A before-you-send-it checklist lists missing fields and flags one-sided gaps neutrally, like an agreement with no termination clause. A built-in clause library covers IP assignment, confidentiality, late payment interest, kill fee and revision rounds, filled with your agreement's own details. Every render carries a one-line note that it is a template, not legal advice. Everything stays on this machine; there is no account and no network call.

Built by theluckystrike.

npm publish for @theluckystrike/mcp-service-agreement is pending, so npx -y @theluckystrike/mcp-service-agreement returns 404 today. Until then, a clone+build is the working path.

Install

Claude Desktop

macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json:

json
{  "mcpServers": {    "service-agreement": {      "command": "npx",      "args": ["-y", "@theluckystrike/mcp-service-agreement"]    }  }}

Claude Code

sh
claude mcp add service-agreement -- npx -y @theluckystrike/mcp-service-agreement

Cursor

~/.cursor/mcp.json (global) or .cursor/mcp.json (project), same entry as Claude Desktop.

Tools

toolwhat it does
agreement_createWrite an agreement: parties, scope, deliverables, rate and payment terms, dates, termination notice, liability cap, jurisdiction. Stores it and returns the rendered Markdown. Returns SA-YYYY-NNNN
agreement_getRead one agreement in full by SA number or client name, with its status history
agreement_listList agreements newest first; filter by status and client
agreement_update_statusMove the agreement exactly one step -- draft, sent, signed, expired -- stamping date and note into its history
clause_libraryThe five built-in clauses: IP assignment, mutual confidentiality, late payment interest, kill fee, revision rounds. Pro: full texts with the agreement's variables filled in
agreement_renderRender for signing: Markdown, or self-contained HTML with print CSS (Pro). Includes the signature block and the template-not-legal-advice line
agreement_checklistThe before-you-send-it checklist: missing fields and one-sided gaps flagged neutrally
license_status / license_activateFree or Pro, and the key

Free vs Pro

FreePro
Active agreements3Unlimited
Core template (parties, services, deliverables, payment, term, termination, liability, jurisdiction, signatures)YesYes
Markdown renderingYesYes
Before-you-send checklistYesYes
Clause libraryTitles and summariesFull texts, variables filled
HTML rendering, print-readyNoYes

The document is never metered. Three active agreements covers a working freelancer's live engagements, and an agreement stops counting the moment it expires, so writing, reading, checklists and Markdown stay free for good. What Pro adds is the full clause library, print-ready HTML, and unlimited active agreements.

Get Pro: https://mcp.zovo.one/buy/service-agreement, $19 one-time for this server, or $39 for the bundle.

Not legal advice

Every rendered agreement ends with one line: "This agreement is a template, not legal advice." The checklist flags gaps neutrally, what the agreement says as written, for both parties, and never tells anyone what the law is or what to do.

Privacy

All data stays local, in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/service-agreement/. Two files: agreements.json, counter.json. Nothing is sent anywhere, there is no account, no API key and no network call in this server at all. License keys are verified offline.

Built by theluckystrike. https://github.com/theluckystrike

Use these docs as an MCP server

Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install:

Source: servers/service-agreement/README.md at commit 55b3f42

Tools

9

agreement_create

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.

Parametersnotescoperequiredclientrequiredclausescurrencyrequiredend_daterate_unitrequiredfreelancerrequiredrate_centsrequiredstart_datedeliverablesrequiredjurisdiction+5 more

agreement_get

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.

Parametersagreementrequired

agreement_list

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.

Parametersclientstatus

agreement_update_status

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.

Parametersdatenotestatusrequiredagreementrequired

clause_library

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.

Parametersagreement

agreement_render

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.

Parametersformatagreementrequired

agreement_checklist

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.

Parametersagreementrequired

license_status

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.

Takes no parameters.

license_activate

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.

Parameterskeyrequired

Version history

4
  1. v0.23.0LatestNov 3, 2026
  2. v0.22.6Oct 14, 2026
  3. v0.22.1Oct 9, 2026
  4. v0.22.0Sep 17, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts