Included on every plan

The contract your AI assistant hasn't read

Claude can draft your reply to a vendor. It just can't tell you what's buried on page 14. Connect CheckMyDoc and it can — uploading the file, running the full review, and walking you through what to push back on.

Connect your assistant Create a free account →

No API key · Works with Claude Desktop, Claude Code, Claude.ai, Cursor, and any MCP client

What it sounds like

No dashboard, no file picker, no waiting on a tab. Just the question you actually had.

You

Here's the vendor MSA they sent back. Anything I should fight?

Your assistant

Uploading it… running the review… it comes back at 71/100 for risk, classified as an MSA. Three things stand out:

Limitation of liabilityHigh
Capped at 3 months of fees, with no carve-out for a data breach.
Auto-renewalHigh
Renews for a full 12 months unless you cancel 90 days out.
IndemnityMedium
You indemnify them for “any third-party claim”; they cover IP only.

You

Give me redlines for the first two I can paste into the thread.

7: document types it recognises
8: compliance checks per review
6: review lenses to focus on
3: redline tones, from gentle to firm

Things to ask once it's connected

Review this MSA and tell me what to push back on.

Score this NDA before I sign it tomorrow.

What did the review say about the liability cap?

Find every contract we've reviewed that has an auto-renew problem.

Draft a reply to their legal team using the suggested redlines.

How many reviews do I have left this month?

Before you sign

Drop the PDF into the chat and ask whether it's market. You get a risk score, the clauses worth arguing about, and wording you can send back — before you've committed to anything.

Mid-negotiation

They sent a redline of your redline. Ask what actually changed and whether their version still protects you, with the exact clause text quoted rather than paraphrased.

Across everything you've signed

Ask which of your reviewed contracts share a problem — auto-renew traps, uncapped indemnity, missing DPAs — and get the list without opening a single file.

Connect it in about a minute

Pick your client. There is no key to generate — you approve the connection in the browser, signed in as yourself.

The server lives at https://checkmydoc.co/api/mcp. Already signed in? Settings → MCP does the same thing.

Open Settings → Connectors
In Claude Desktop, go to Settings, then Connectors, then Add custom connector.
Paste the server URL
Name it CheckMyDoc and paste this as the URL.
Server URL
```
https://checkmydoc.co/api/mcp
```
Approve the connection
The first request opens CheckMyDoc in your browser. Sign in with your usual account and approve — there is no key to paste.
That's it
Ask it to review a contract. Anything it runs shows up in your history like any other review.

Seven tools, scoped to your workspace

Your assistant sees exactly these and nothing else. Every review it runs shows up in your history like any other.

list_review_templates
The review lenses available — vendor MSA pushback, GDPR Article 28, and the rest.
upload_contract
Send a contract as plain text or file bytes (PDF, DOCX, DOC, TXT — up to 25 MB).
review_contract
Run the full analysis: document type, risk score, findings, redlines, compliance pass.
get_review
Re-read a finished review by document id or review id.
list_reviews
Search past reviews by text, document type, or risk score.
get_document_text
The text extracted from a document, so the assistant can quote exact wording.
get_quota
Plan, reviews used, and reviews remaining — before one gets spent.

What it can't do

Reach anything outside the workspace you approved — no other team's documents, no billing, no account settings.
Spend more than your plan allows. Reviews come out of the same document allowance as the dashboard, and the assistant can check what's left before using one.
Stay connected after you disconnect it. Revoking takes effect on the app's next call.
Hold your password. Authorization is OAuth 2.1 with PKCE against your CheckMyDoc sign-in, so an app only ever holds a short-lived token scoped to what you approved.
Give legal advice. It surfaces risks and suggested wording; the judgement call stays yours.

Questions

What is an MCP server?: The Model Context Protocol is a standard way for an AI assistant to use an outside service. Connecting ours gives your assistant a set of CheckMyDoc tools it can call on your behalf — upload a contract, run a review, read the findings — instead of you copying text back and forth.
Do I need an API key?: No. Your client sends you to CheckMyDoc, you sign in with the account you already have and approve the request, and it receives its own short-lived access. Nothing to generate, paste, or rotate.
Which plans include it?: All of them, free included. Reviews an assistant runs come out of the same monthly document allowance as reviews you run yourself, so what limits you is your plan's document count — not access to MCP. The REST API is the separate, Pro-and-up product for calling the pipeline from your own code.
What can a connected app actually see?: Only the workspace you approved, and only through the seven tools listed above. It cannot reach another team's documents, your billing, or your account settings. Reviews it runs appear in your history exactly like the ones you run yourself.
How do I disconnect it?: Settings → MCP lists every app you've approved, with a Disconnect button. Revoking takes effect on that app's next call.
Is the answer legal advice?: No — it's analysis. It flags what's unusual, what's one-sided, and what's missing, in plain English, so you can decide what to argue about and when to call a lawyer.

Building on the pipeline yourself instead? The REST API covers the same ground on Pro and Scale.

Your assistant is already open. Give it the contract.

Paste one line, approve the prompt, and ask your next contract question where you were already going to ask it.

Create a free account Connect your assistant