Docs ยท Lindy
Precleared in Lindy
Lindy agents can use tools from any MCP server that is reachable over public HTTPS. Add Precleared as one and your Lindy can check whether a cold email to an address is allowed before it sends it. Each check gives a verdict, the rule quoted with its source, what the footer must include and a signed receipt. It covers the UK, US, Canada, Germany, France, Australia, Ireland, the Netherlands, Spain, Italy, Latvia, the United Arab Emirates, Egypt and Qatar.
Connect it (about two minutes)
- In Lindy, go to Integrations, click + Add and choose MCP.
- In Connect MCP server, paste the Server URL https://precleared.dev/mcp and set the Display name to Precleared.
- Authentication: none is needed to start. For steady use, get a free key, open Advanced and add it as an Authorization bearer token. Lindy runs agents on shared servers, so without a key your checks share the free allowance with other Lindy users.
- Click Connect. Precleared appears with its tools: contact_check, verify_receipt, suppress_contact and link_account, all switched on. If you added a key, you can switch off link_account: it is only for connecting an account by signing in.
- Optional: under Guardrails, set contact_check and verify_receipt to Always allow so checks don't wait for you, and leave suppress_contact on Ask for approval, since it changes your opt-out list. Under Availability, choose Your workspace if your team should use it too.
Precleared's server uses the Streamable HTTP transport, which is what Lindy connects to.
Troubleshooting: if Lindy shows 0 available tools, check the URL is exactly https://precleared.dev/mcp.
Tell the agent when to use it
Add this to the agent's core instructions:
Before the first cold or marketing email to anyone who is not already a customer, call contact_check (MCP: Precleared) for that address, with sender_country, address_source and pitch. If you have the draft, pass it as email so the footer is checked too. Send only when the verdict is ok_to_email, with a footer that meets footer_text. If the verdict is consent_needed or blocked, don't send, and follow next_step. Treat unknown as consent_needed. Keep the receipt id with the lead.
What each verdict means
- ok_to_email: the address may be emailed. Follow the footer requirements in footer_text.
- consent_needed: don't send. Follow next_step.
- blocked: don't send. Follow next_step.
- unknown: treat it as consent needed. Don't send until the missing facts are resolved.
Receipts
Each check returns a signed receipt. Keep its id with the lead. Use verify_receipt to fetch it. See Verifying a receipt for signature verification.
What the agent sends
Only the recipient's address and the facts you pass: your country, where the address came from, the pitch and, if you add them, the company name, the person's name and the draft. The draft is not stored; only its hash goes on the receipt. Nothing is sent to the recipient. More on how data is handled: /security.
Allowances
Without a key, the agent uses the free daily allowance over MCP. With a free key it gets its own 100 checks a day over MCP. Over MCP that stays at 100 a day after the key's 14-day trial ends. No card needed. For more, see /buy.
Precleared's answers are decision support with sources, not legal advice.