Service Contract is answering right now. Last checked 4 min ago. It exposes 9 tools. Last commit 22 Sep 2026.
Write a freelance service contract: scope, deliverables, rate, termination, liability, signatures.
Uptime history
2 hours of history
2 hours agonow
100.0%
Uptime 24h
6 of 6 checks
9
Tools
read from the server
680 ms
Response time
average over 24h
0
Stars
last commit 22 Sep 2026
Nothing serious here today
Today is the operative word: we check Service Contract 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 4 min ago.
run in your terminal
claude mcp add service-contract --transport http https://mcp.zovo.one/mcp/service-contract~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"service-contract": {
"url": "https://mcp.zovo.one/mcp/service-contract"
}
}
}~/.codex/config.toml
[mcp_servers.service-contract]
url = "https://mcp.zovo.one/mcp/service-contract".cursor/mcp.json
{
"mcpServers": {
"service-contract": {
"url": "https://mcp.zovo.one/mcp/service-contract"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"service-contract": {
"url": "https://mcp.zovo.one/mcp/service-contract"
}
}
}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-contract | streamable-http | answering | 670 ms | 4 min ago |
Alternatives to Service Contract
same job, measured the same wayService Agreement
by theluckystrike
Service agreements for freelancers: scope, deliverables, rate, termination and liability caps.
LeadProof Sales Agent
by chatgpt-jessesay-leadproof
Audit lead-delivery workflows, find reliability gaps, and generate a LeadProof integration plan.
Configcat
by configcat
Enables AI agents to interact with ConfigCat, a feature flag service for teams.
Ebenova Scope Guard
by dgtalquantumleap-ai
AI contract scope violation detector. Detect scope creep, draft responses.
Consultant.dev
by consultant
Search live consulting, contractor, and freelance assignments worldwide. Account required.
MisarMail MCP Server
by misar-ai
Send transactional email, run campaigns, manage contacts and automations, audit deliverability.
Contract Scanner
by lordbasilaiassistant-sudo
Smart contract security scanner — vulnerabilities, risk scores, and calldata decoding
Android Puppeteer MCP
by pedro-rivas
MCP server for Android automation with UI interaction, screenshots, and device control
Service Contract — questions
Answers built from our own checks of this server.
What can Service Contract 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 Contract 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 Contract working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 6 of 6 checks got a reply (100.0%), average response time 680 ms. The bar chart above shows every period we have measured.
How do I connect Service Contract?
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 Contract need an API key?
No. Service Contract 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 Contract?
It answers our handshake in 680 ms on average, which is faster than 19% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Service Contract 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.