Service Agreement MCP server

• agreement_checklistFree

  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.

• agreement_createwrite actionFree

  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.

• agreement_getFree

  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.

• agreement_listFree

  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.

• agreement_renderFree

  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.

• agreement_update_statuswrite actionFree

  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.

• clause_libraryFree

  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.

• license_activateFree

  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.

• license_statusFree

  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.

• –Code scanpackage could not be scannedn/a
• Live reliabilityremote reachable in 178ms20/20
• Tool poisoning9 tool descriptions checked15/15
• Auth qualityAPI key sent as a header8/15
• Maintenancelast push 1 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Grade history

• 2026-09-19restoreC → Ascore 88

Service Agreement: common questions

Is Service Agreement MCP server safe?

Yes, by our scan: it is graded A (88/100). Read the Service Agreement safety report

How do I install Service Agreement?

It runs remotely at mcp.zovo.one. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Service Agreement need an API key?

Yes. The registry entry asks for MCP_LICENSE_KEY, Authorization.

Is Service Agreement maintained?

The last commit was in the last day (2026-09-19). The latest release is v0.22.0.

Is Service Agreement up?

100% of our last 3 checks got an answer. We check remote servers about four times a day.