A
licenseNot graded
qualityF
maintenanceEnables AI agents to create, sign, and enforce binding agreements with deliverables, deadlines, penalties, and a full lifecycle state machine.
2
MIT
mcp-service-agreement
Related Servers
Alternatives to mcp-service-agreement
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceFacilitates contract and template management for eSignatures, enabling users to create, send, update, and manage contracts and templates with customizable options through a user-friendly interface.1320 PyPI40MIT
- AlicenseAqualityBmaintenanceFill standard legal agreement templates (NDAs, SAFEs, NVCA docs, employment, cloud terms) and produce DOCX files.32,480 npm55Apache 2.0
- AlicenseNot gradedqualityCmaintenanceBlockchain-anchored e-signatures. Create, send, negotiate, and verify legally binding agreements — every signature anchored to XRPL + Bitcoin with public verification. Agents can pay autonomously.MIT
Formify MCPofficial
AlicenseNot gradedqualityAmaintenanceEnables AI agents to create fillable PDFs, send contracts for e-signature, verify signers via BankID or ID scans, and track post-send document workflows.5MIT- FlicenseNot gradedqualityCmaintenanceEnables generating startup legal documents such as NDAs, MSAs, DPAs, privacy policies, and offer letters from attorney-drafted templates, with downloads in PDF, ODT, or Markdown through MCP and no account required.-
TDQS
A4.1/5.0
Scored across 9 tools
Disambiguation4/5
The agreement tools are split by action (create/get/list/update_status/render/checklist) and the license tools are clearly separate, so an agent can usually pick the right one. The only mild ambiguity is that agreement_create and agreement_render both produce Markdown output, while agreement_checklist could be mistaken for a validation step rather than a read-only check.
Naming Consistency4/5
Most tools follow an agreement_<verb pattern, and license_status/license_activate keep the same convention. The exceptions are agreement_checklist and clause_library, which use nouns instead of actions, creating a small but noticeable deviation.
Tool Count5/5
Nine tools is well-scoped for a service-agreement server: CRUD-like agreement operations, rendering, checklist validation, a clause library, and license management all earn their place. The count feels intentional rather than bloated or sparse.
Completeness3/5
The set covers creating, reading, listing, status transitions, rendering, validation, clause lookup, and license activation, so the main lifecycle is represented. A clear gap is the absence of any way to update an agreement's content after creation; agents cannot fix a mistake or revise terms without creating a new agreement.
Maintenance
ActivityNo data
ResponsivenessNo issues