PAKT MCP Server
Related Servers
Alternatives to PAKT MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that gives Claude safety-gated access to SpotDraft contracts, enabling querying and managing contracts, templates, counterparties, obligations, and analytics through natural language.19MIT

BitsBound MCP Serverofficial
AlicenseAqualityDmaintenanceEnables AI-powered contract analysis with partner-level redlines and real OOXML Track Changes for Claude Desktop and Claude.ai.12208 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables users to query, create, and manage contracts in plain English from any MCP client, including drafting and sending agreements, tracking renewals and signers, and building templates. It supports OAuth-authenticated workflows with safe defaults such as creating drafts and confirming before sending or changing live agreements.MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to search and retrieve contract intelligence over public contract data, with agent skills for precedent lookup, negotiation checks, and risk flagging, all with verification and citations.-
- FlicenseAqualityBmaintenanceEnables LLMs to ingest and analyze legal agreements, compute risk scores, and monitor non-compliant clauses through MCP tools like ingest, fetch_contracts, and run_analysis.4-
- AlicenseNot gradedqualityDmaintenanceEnables Claude or Cursor to act as a contract analyst by providing tools for document fetching, clause segmentation, span verification, and risk taxonomy lookup, with no server-side LLM calls or document retention.MIT
TDQS
Scored across 4 tools
list_contracts, get_contract, analyze_contract, and compare_amendment each target a distinct action and resource. The only mild overlap is that analyze_contract returns 'the same overview as get_contract,' which could blur read vs. upload boundaries, but their primary intents remain clear.
All four tools follow a strict verb_noun snake_case pattern: list_contracts, get_contract, analyze_contract, compare_amendment. Consistent and predictable throughout.
Four tools is a tight, focused set for a contract-risk analysis server. It sits at the low end of the ideal range but each tool earns its place and none is redundant.
Core workflows (list, read overview, upload/analyze, compare amendments with create-or-replace logic) are covered. Gaps remain around deleting contracts, updating metadata, and standalone amendment listing, but these are minor workarounds rather than dead ends.