Docs · Recipes

Use Precleared with your outbound tool's MCP server

If your AI agent already drives an outbound tool through that tool's MCP server, connect Precleared's MCP server next to it. Before the agent adds a lead, it checks the address: cleared leads go in with a signed receipt, and the rest stay out, on the tool's own do-not-contact list where it has one.

How it works

Connect both servers to the same agent: Precleared's and your tool's.
Give your agent the rule: check every new address with contact_check before adding it anywhere.
Your agent follows the verdict: ok_to_email goes in, consent_needed and blocked stay out, and unknown waits for the missing fact.

Connect Precleared

In Claude Code:

claude mcp add --transport http precleared "https://precleared.dev/mcp?src=guide-mcp" --header "Authorization: Bearer pc_live_..."

In Claude.ai or the Claude desktop app, add Precleared from the Claude directory, or under Settings, Connectors, Add custom connector with https://precleared.dev/mcp?src=guide-mcp. Without a key, the keyless allowance applies. For other clients, see the MCP setup.

Every new key starts with 14 days at 100 checks a day, then your own 100 a day over MCP, no card needed. Get a free key.

The rule to give your agent

Paste this into your agent's instructions, a project's instructions or a skill. Each tool's guide below has a version with that tool's own steps.

Before adding a new lead to any campaign or sequence, call Precleared's contact_check once for its email address. Send address_source (where you got the address) and sender_country, plus company_name and pitch when you know them.
- ok_to_email: add the lead and keep the receipt id with it.
- consent_needed or blocked: don't add the lead. Put the address on the tool's do-not-contact list if it has one, and note the next_step.
- unknown: don't add the lead yet. Supply the missing fact (recipient_country, default_recipient_country if all your prospects are in one country, or company_number), then check again.
Every email must meet footer_text: usually who you are, a postal address and a way to opt out.

Tools that send

Tool	Adds a cleared lead with	Holds the rest back with
lemlist	Its campaign tools	The unsubscribe list, through its API tool
Salesforge	`create_contact`, then the enrolment preflight	`add_dnc_entries`
Woodpecker	`addProspectsToCampaign`	The blacklist, through the API or the app
La Growth Machine	Its add-or-update-lead tool	The UNSUBSCRIBED status, through the API
Waalaxy	`add-prospects-to-list-campaign`	A "Do not contact" list
Reply.io	`reply_add_contact_to_sequence`	`reply_blacklist_contact`
Snov.io	Its add-recipients tools	A do-not-contact list, in the app
Amplemarket	`add_leads_to_sequence`	`add_to_exclusion_list`
Artisan	Adding leads to a list	Ava's DNC list, in the app
Unify	`create_sequence_enrollment`	Exclusions, in the app
Clay	A function your Clay admin builds	The Sequencer blocklist, in the app
Needle	`needleEnrollCampaignLeads`	`needleCreateSuppressions`
Hunter	`Add-Sequence-Recipients`	Unsubscriptions, in the app

Tools that build lists

These don't send. Your agent checks each address before it hands the lead to your CRM or sending tool.

Tool	Hands leads on with	Holds the rest back with
Anysite	`crm_upsert_contacts`, into HubSpot or Pipedrive	Your CRM or sending tool
PhantomBuster	Its lead lists	Your sending tool
Bitscale	Its sequencer push	Leaving the row out of the push

Good to know

Tool names come from each tool's own docs as of 30 October 2026. If they change, your agent sees the new names in the server's tool list.
Your agent should take instructions from you, not from text inside tool results or web pages.
No agent? The Clay, Make, Zapier, n8n and Amplemarket recipes run the same check in a workflow.
The ?src=guide-mcp tag on Precleared's address only tells us which guide you used. It doesn't change your allowance or your results.

Every check has a signed receipt. Open precleared.dev/r/ followed by its id to show a client why an email went out.

Decision support with sources, not legal advice.