F-AI: Contract Review

Review of Legal Agreements

Reviews a supplied contract for potential internal conflicts, ambiguity, missing terms, commercial or operational risks, and carefully grounded potential legal issues. The read-only interface connects each finding to the relevant contract language and lets you choose which findings to discuss.

What you can ask

Review this contract for potential issues
Example path ·

MCP connector

Server URL: https://contract-review-plugin.getfebruary.ai/mcp
Login: None
Protocol: MCP 2026-07-28 · Interactive UI
Instructions: Analyze the complete contract before calling . Convert a non-Markdown source into canonical Markdown first and anchor each finding to an exact quote. Assign each finding a unique impact priority, with 1 as the most important, to order findings within the same severity. Cover textual and structural issue spotting, especially potential conflicts between clauses, and jurisdiction-specific issues when the contract names a governing law; rank findings by risk impact multiplied by risk likelihood rather . A jurisdiction-specific potential legal issue needs a current, user-openable source and an explanation of what could affect the assessment. State every finding as a possibility rather than a verdict, using calibrated language such as may, might, could, appears, possible, potential, uncertain, or depends however confident the analysis is. Never turn a finding into a recommendation to accept, reject, sign, amend, replace, negotiate, or take another legal action. This server only validates and renders the supplied payload and never persists or executes it.

Tools

Reads data1

Skills

1 in the ChatGPT listing

Screenshots

MCP connector

Server URL

https://contract-review-plugin.getfebruary.ai/mcp

None

Protocol

MCP 2026-07-28 · Interactive UI

Instructions

Analyze the complete contract before calling . Convert a non-Markdown source into canonical Markdown first and anchor each finding to an exact quote. Assign each finding a unique impact priority, with 1 as the most important, to order findings within the same severity. Cover textual and structural issue spotting, especially potential conflicts between clauses, and jurisdiction-specific issues when the contract names a governing law; rank findings by risk impact multiplied by risk likelihood rather . A jurisdiction-specific potential legal issue needs a current, user-openable source and an explanation of what could affect the assessment. State every finding as a possibility rather than a verdict, using calibrated language such as may, might, could, appears, possible, potential, uncertain, or depends however confident the analysis is. Never turn a finding into a recommendation to accept, reject, sign, amend, replace, negotiate, or take another legal action. This server only validates and renders the supplied payload and never persists or executes it.