BRAINIAC Contract Operations
software.brainiac/contract-operations · v1.0.1 · MCP 2025-11-25
Paid Contract Operations API via x402. Unpaid tool calls return 402.
Reachability
reachable
checked 2026-11-21 05:31 UTC
Registry status active
Tools pinned 10
041c2cf11d29
Tools last changed
2026-11-21
Provenance
Registry namespace software.brainiac
(domain verified by the official registry)
Website
https://www.brainiac.software
Remote endpoints
https://www.brainiac.software/mcp/contract-operations (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-11-21 05:31 | tools changed | 0 added, 0 removed, 10 changed |
| 2026-11-20 05:30 | first capture | 10 tools pinned |
Pinned tool definitions (10)
| Tool | Description |
|---|---|
| contract-operations_clause-extract | Extract numbered clauses, parties, defined terms, and a governing-law sentence from supplied contract text or a text-based PDF when reviewing a contract or change. Each item keeps a source excerpt. Missing headings stay unavailable.... |
| contract-operations_obligation-extract | Extract sentences that use shall, must, agrees to, is required to, or undertakes to, and name the party stated before the verb. Sentences that only say may are not turned into obligations. Call with optional text, file, clauses. Returns... |
| contract-operations_deadline-extract | Extract stated periods, notice periods, and unambiguous calendar dates when reviewing a contract or change. Slash dates are not guessed, and a deadline is not created when the text gives no number or date. Call with optional text, file,... |
| contract-operations_renewal-risk-check | Read renewal and expiration wording that is actually printed when reviewing a contract or change. A notice date is calculated only from a stated expiration date and a stated notice period. Renewal wording is flagged as a potential risk,... |
| contract-operations_missing-clause-check | Compare the contract with a checklist or with provisions supplied for a named standard when reviewing a contract or change. A standard name alone does not create required clauses, and similar wording is not inferred. Call with optional... |
| contract-operations_version-diff | Compare two supplied contract versions by clause number or heading when reviewing a contract or change. Whitespace and letter case alone are not reported. Clauses are not matched by meaning. Call with base and revised. Returns... |
| contract-operations_change-impact | Label meaningful version changes as a date, a stated period, an obligation verb, or an added or removed clause when reviewing a contract or change. The legal effect of a change is not decided. Call with base and revised. Returns... |
| contract-operations_party-obligations | Group extracted obligations under the party named before shall, must, or agrees to. An obligation that names no party stays unassigned. Call with optional text, file, clauses. Returns checkedAt, legalAdvice, complianceDetermined,... |
| contract-operations_risk-summary | Flag renewal, indemnity, unlimited-liability, and termination-for-convenience wording that is present in the text when reviewing a contract or change. These are potential risks, not a legal opinion or a risk score. Call with optional... |
| contract-operations_compliance-review | Combine clause, obligation, deadline, renewal, checklist, party, and risk checks when reviewing a contract or change. checklist_satisfied means the supplied phrases were found. It is not a legal compliance determination. Call with... |
Get alerted when this changes.
Email the moment software.brainiac/contract-operations drifts, dies, or revives.
Status badge
[](https://toolpin.dev/servers/software.brainiac/contract-operations)
Maintain this server? Add the badge to your README. It links your users to this live status page.