compare_contract_risk — ClausePilot MCP Tool
compare_contract_risk
(compare contract risk) is one of 18 tools on the
ClausePilot
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call compare_contract_risk from your client
- Claude Code ClausePilot compare_contract_risk run in your project directory
- Claude Desktop ClausePilot compare_contract_risk ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ClausePilot compare_contract_risk ~/.cursor/mcp.json
- VS Code ClausePilot compare_contract_risk .vscode/mcp.json
- Zed ClausePilot compare_contract_risk ~/.config/zed/settings.json
- Windsurf ClausePilot compare_contract_risk ~/.codeium/windsurf/mcp_config.json
- Cline ClausePilot compare_contract_risk ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ClausePilot compare_contract_risk ~/.gemini/settings.json
- Grok ClausePilot compare_contract_risk .mcp.json (in your project root)
- ChatGPT ClausePilot compare_contract_risk Settings → Connectors → Advanced → Developer mode
- Claude.ai ClausePilot compare_contract_risk Settings → Connectors → Add custom connector
- LangChain ClausePilot compare_contract_risk pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http clausepilot https://clausepilot-pearl.vercel.app/mcpOther tools on this server
- get_clausepilot_payment_info
- list_clausepilot_paid_tools
- analyze_contract_risk
- extract_renewal_deadline
- find_contract_penalties
- extract_contract_obligations
- summarize_contract_for_agents
- triage_contract
- triage_pdf_contract
- triage_contract_batch_10
- scan_contract_portfolio_50
- scan_contract_portfolio_200
- review_vendor_contract_risk
- check_saas_terms
- check_nda_clauses
- extract_employment_terms
- extract_payment_terms
This list was read from the server itself, by connecting to it and calling tools/list on 6 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.