Service Agreement is answering right now. Last checked 12 min ago. It exposes 9 tools. Last commit 18 Sep 2026.
Service agreements for freelancers: scope, deliverables, rate, termination and liability caps.
Uptime history
22 hours of history
22 hours agonow
100.0%
Uptime 24h
81 of 81 checks
9
Tools
read from the server
188 ms
Response time
average over 24h
0
Stars
last commit 18 Sep 2026
Nothing serious here today
Today is the operative word: we check Service Agreement every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.
run in your terminal
claude mcp add service-agreement --transport http https://mcp.zovo.one/mcp/service-agreement~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"service-agreement": {
"url": "https://mcp.zovo.one/mcp/service-agreement"
}
}
}~/.codex/config.toml
[mcp_servers.service-agreement]
url = "https://mcp.zovo.one/mcp/service-agreement".cursor/mcp.json
{
"mcpServers": {
"service-agreement": {
"url": "https://mcp.zovo.one/mcp/service-agreement"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"service-agreement": {
"url": "https://mcp.zovo.one/mcp/service-agreement"
}
}
}Available tools 9
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
agreement
agreement_checklist
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_create
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_get
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_list
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_render
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_status
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.
license
license_activate
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_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.
clause
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.zovo.one/mcp/service-agreement | streamable-http | answering | 45 ms | 12 min ago |
Alternatives to Service Agreement
same job, measured the same wayLeadProof Sales Agent
by chatgpt-jessesay-leadproof
Audit lead-delivery workflows, find reliability gaps, and generate a LeadProof integration plan.
Jira Alerts (JSM Operations)
by rrvrs
MCP server for Jira Service Management Operations — alerts, on-call schedules and responders
Causely
by causely
Causal reasoning for reliability: root cause, blast radius, and service health for agents.
Ugc Brief MCP
by closermethod
Turn a brand brief into deliverables, shot lists, and the right UGC format, catching scope traps.
Domain & Company Intel MCP
by datakoot
Domain intel for AI agents: RDAP registration, DNS, email deliverability, tech stack.
Desktop Commander
by wonderwhy-er
MCP server for terminal commands, file operations, and process management
ScopeGate
by alifanov
Permission gateway for AI agents: scoped MCP endpoints over 27 services, audited and revocable.
I
Bearing Local Business
by nickoc
Reference MCP server: a demo bakery agents can query for hours, menu, availability, and orders.
Service Agreement — questions
Answers built from our own checks of this server.
What can Service Agreement do?
It exposes 9 tools, read directly from the server on our last check. Among them: agreement_checklist, agreement_create, agreement_get, agreement_list, agreement_render, agreement_update_status and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Service Agreement mostly used for?
Its tools cluster around agreement and license. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Service Agreement working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 81 of 81 checks got a reply (100.0%), average response time 188 ms. The bar chart above shows every period we have measured.
How do I connect Service Agreement?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Service Agreement need an API key?
No. Service Agreement completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Service Agreement?
It answers our handshake in 188 ms on average, which is faster than 69% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Service Agreement open source?
Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.