Contract Analysis

com.bitsboundPublished by bitsbound.comv1.0.6Updated Oct 24, 2026

AI contract analysis with partner-level redlines, OOXML Track Changes, and risk analysis.

VerifiedSTDIODesktop onlyProductivity & Workflow Business & Commerce

Server details

Identifier: com.bitsbound/contract-analysis
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to bitsbound.com. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.bitsbound%2Fcontract-analysis.svg)](https://sourceweft.com/mcp/com.bitsbound%2Fcontract-analysis?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Analyzes contracts, producing partner-level redlines as real Word Track Changes, clause extraction, risk scoring and negotiation emails.

What you can do: Upload and analyze a contract, producing a redlined DOCX with real OOXML Track Changes
Check analysis progress and retrieve the resulting deliverables
Extract specific clause types from a contract
Generate a professional negotiation email
Apply deal context such as value, industry and aggressiveness level to the analysis
When to use it: Useful when you review contracts and want an assistant to draft redlines, pull out clauses, score risk and prepare negotiation emails, especially inside Claude Desktop or Claude.ai.
Requirements: Runs locally via npx from the npm package @bitsbound/mcp-server, or remotely over HTTP with OAuth 2.0 for Claude.ai connectors. Requires a BitsBound API key, supplied as the BITSBOUND_API_KEY environment variable locally or as the OAuth client secret remotely. Contracts are uploaded as DOCX files.

Before you install

Requires a BitsBound API key, which is used as the OAuth client secret for remote access. Contract files and deal context are sent to BitsBound's service for analysis, so confidential documents leave your machine. The server produces redlined documents and negotiation emails that should be reviewed before use.

Installation

In SourceWeft

Open Contract Analysis in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

BitsBound MCP Server

AI-powered contract analysis with partner-level redlines for Claude Desktop and Claude.ai.

Features

Contract processing with partner-level redlines
Real OOXML Track Changes (w:ins/w:del) - not markup, actual Word revisions
Clause extraction and analysis
Risk scoring and favorability dashboards
Negotiation email generation
Deal context awareness (value, industry, aggressiveness)

Installation

Claude Desktop (Recommended)

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):

json

{  "mcpServers": {    "bitsbound": {      "command": "npx",      "args": ["-y", "@bitsbound/mcp-server"],      "env": {        "BITSBOUND_API_KEY": "sk_live_your_api_key"      }    }  }}

{  "mcpServers": {    "bitsbound": {      "command": "npx",      "args": ["-y", "@bitsbound/mcp-server"],      "env": {        "BITSBOUND_API_KEY": "sk_live_your_api_key"      }    }  }}

Get your API key at: https://account.bitsbound.com/api-keys

Claude.ai Custom Connectors (HTTP/OAuth 2.0)

For remote MCP access via claude.ai:

Name: BitsBound
URL: https://bitsbound-mcp-server.onrender.com/mcp
Client ID: bitsbound-mcp
Client Secret: Your BitsBound API key (sk_live_xxx...)

OAuth 2.0 endpoints:

Discovery: /.well-known/oauth-authorization-server
Authorize: /oauth/authorize
Token: /oauth/token

Tools

Tool	Description
`process_contract`	Upload and analyze a contract - produces redlined DOCX with Track Changes
`get_analysis_status`	Check analysis progress and retrieve deliverables
`extract_clauses`	Extract specific clause types from a contract
`generate_negotiation_email`	Create a professional negotiation email

Example Usage

Claude will ask for:

Contract file (drag & drop DOCX)
Deal context (value, industry)
Aggressiveness level (1-10)
Email recipient details

Registry

MCP Registry: io.github.taytrom/bitsbound-contract-automation
npm: @bitsbound/mcp-server

Support

Email: [email protected]
Website: https://bitsbound.com
Privacy Policy: https://www.bitsbound.com/privacy
DPA: https://www.bitsbound.com/dpa

License

MIT - BitsBound, Inc.

Source: README.md at commit d5cc5a7

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.6LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts
Declare a license in the repository or the registry entry.