ClauseProof

Inspiration

What it does

How we built it

Challenges we ran into

Accomplishments that we're proud of

What we learned

What's next for ClauseProof

Inspiration

Contracts rarely fail because nobody summarized them. They fail because risk, authority, and action get blurred together. ClauseProof explores an open web where a person and an AI agent can inspect the same contract state without allowing fluent model output to masquerade as human approval.

What it does

ClauseProof turns a high-stakes agreement into a source-grounded decision room. Documents are read locally, including OCR for image documents. Deterministic rules keep the exact governing clause beside each finding. A human can resolve or explicitly accept risks, record a case-specific approval, and prepare an unsigned signature-packet receipt.

The synthetic Northstar supply agreement demonstrates auto-renewal, exclusivity, payment, cure, and liability findings. Uploaded bytes and extracted text stay in the browser.

Why WebMCP

The live page exposes six narrow tools over the same state the human sees:

1. get_case_summary
2. list_open_risks
3. propose_risk_resolution
4. record_human_risk_decision
5. approve_case_decision
6. prepare_signature_packet

Each tool is registered with document.modelContext.registerTool, uses a closed input schema, describes its effects, and returns a structured receipt. An agent proposal remains a proposal. Approval requires a visible human decision, and signature preparation always reports sent: false and signed: false.

How we built it

React and TypeScript power the shared browser workflow. PDF.js and Tesseract.js handle local text and OCR. Xano provides the durable synthetic case, audit events, evidence receipts, idempotent bootstrap, and five deployed endpoints. SerpApi runs one bounded server-side counterparty query through Xano; the live proof returned nine organic results and evidence receipt 1 without exposing the key to the browser.

Vitest covers the authority boundaries and deterministic extraction. Netlify serves the public HTTPS build.

Challenges

The hardest problem was making agent actions useful without collapsing capability into authority. We separated analysis, proposal, human risk decisions, case approval, signature preparation, sending, and signing into independently verifiable states.

Accomplishments

• One shared human-and-agent workflow instead of an agent-only chatbot
• Exact-source findings with local OCR
• Six working WebMCP tools over real product state
• Explicit approval and non-action receipts
• Live Xano and SerpApi integration
• Public MIT source and reproducible deployment artifacts

What we learned

WebMCP is strongest when it exposes a product's real workflow, keeps effects narrow, and makes meaningful transitions independently reviewable. The best agent experience is not maximum autonomy; it is useful capability with trustworthy authority boundaries.

What's next

Add authenticated private rooms, versioned redlines, provider-backed PDF generation, and a human-controlled e-sign handoff. Those providers will not be claimed until their live calls and terminal receipts are proven.

Built With

• serpapi
• xano