Back to Browse
Free
Server data from the Official MCP Registry
One MCP server for the contract-ops suite: all nine local-first CLIs as agent tools.
About
One MCP server for the contract-ops suite: all nine local-first CLIs as agent tools.
Security Report
8.2
Low Risk8.2Low RiskWell-designed MCP server with strong security controls. The code implements explicit human-gating for sensitive signing operations through an allowlist that blocks mutating commands while permitting read-only operations. File path arguments are properly confined to a configurable base directory. The main findings are minor: missing env_vars documentation, a broad exception handler, and verbose output of error details that could leak information. Permissions align well with the server's purpose of wrapping contract-operations CLIs. Package verification found 1 issue.
7 files analyzed · 5 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-drbaher-contract-ops-mcp": {
"args": [
"-y",
"contract-ops-mcp"
],
"command": "npx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
contract-ops-mcp
One MCP server for the whole contract-ops CLI suite — wire it up once and an agent (Claude, Cursor, Codex, …) gets all nine local-first CLIs as tools: extract, draft, lint, compare, convert, review, and the template + signed-contract vaults. Signing stays human-gated.
Run this
// e.g. Claude Desktop / Cursor MCP config
{
"mcpServers": {
"contract-ops": { "command": "npx", "args": ["-y", "contract-ops-mcp"] }
}
}
The CLIs themselves must be installed (the server shells out to them). Fastest way to get all nine:
curl -fsSL https://cli.drbaher.com/install.sh | sh # local
# …or run the server + CLIs in one container: ghcr.io/drbaher/contract-ops
Call suite_status any time to see which CLIs are present and how to install any that aren't.
Tools
Curated, ergonomic tools (typed inputs, JSON out) for the common operations, plus two escape hatches for the long tail:
| Tool | What it does |
|---|---|
extract_contract | Any contract (.md/.txt/.html/.docx/.pdf) → structured JSON (parties, dates, clauses, …) |
lint_contract | Internal-consistency findings (placeholders, broken refs, defined-term/numbering/date defects) |
compare_versions | Clause-aware drift between two versions (exit 0 clean · 2 substantive · 3 cosmetic · 4 moved) |
fill_template | Fill a template's placeholders with typed params (deterministic) |
convert_to_pdf | DOCX → PDF (needs a PDF backend, e.g. LibreOffice) |
review_nda | Score an NDA against a house playbook, with evidence |
template_vault_find / template_vault_get | Search / resolve versioned templates (read-only) |
contract_vault_query / contract_vault_due / contract_vault_risk | Query the signed-contract register; project renewal/notice deadlines; renewal-exposure (read-only) |
verify_signature / verify_receipt / audit_show | Verify a signed PDF / a receipt bundle / walk the audit log (read-only) |
catalog(cli) | Return any CLI's full --catalog json — discover the long tail |
run(cli, args) | Escape hatch: run any suite CLI with raw args (no shell) |
suite_status | Which CLIs are installed (+ versions) and how to install the rest |
The curated set and catalog/run are discovery-driven — they ride the suite's uniform --catalog json contract, so they stay in sync as the CLIs evolve.
Safety
- Signing is human-gated. Only sign-cli's read/verify operations are exposed (
verify_signature,verify_receipt,audit_show) — never request-create or sign. This is enforced: therun/catalogescape hatches reject anysignsubcommand outside a read-only allowlist, so request-create/send/sign/approve can't be reached here. Those stay behind sign-cli's own MCP server with its per-signer approval tokens, so this server can't become an unguarded signing path. - Filesystem lockdown. File-path arguments to the curated tools are confined to
CONTRACT_OPS_MCP_BASE_DIR(default: the working directory). Set it to widen the sandbox. - No shell. CLIs are invoked with
execFile(no shell interpolation).
License
MIT. Part of the contract-ops CLI suite. See AGENTS.md for the agent contract.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
80.0K
Stars
4
Installs
6.5
Security
No ratings yet
Local
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
80.0K
Stars
4
Installs
5.3
Security
No ratings yet
Local
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
137
Stars
496
Installs
8.0
Security
4.8
Local