Official MCP RegistryListed
Precleared Contact Check
Cold email compliance check across 8 countries: per-address verdict, rule cited, signed receipt.
First seen 12 Oct 2026. Evidence as of 25 Oct 2026.
2
Tools
From an anonymous probe
1
Source listings
Each with its own history
19
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| contact_check | Is it legal to send a cold or marketing email to this person? Check before the first email to any new lead, prospect or contact who is not already a customer, one call per address: a compliance check for B2B sales outreach, prospecting and lead lists. Whether it is allowed, or needs consent first, turns on facts you cannot see in the address, such as whether a UK recipient is a limited company or a sole trader, so it looks them up live (UK Companies House) and applies UK PECR and GDPR, US CAN-SPAM, Canadian CASL, German UWG, French CPCE, Australia's Spam Act, Ireland's ePrivacy Regulations and the Dutch Telecommunicatiewet. Returns a verdict (ok_to_email, consent_needed, blocked or unknown), the rule quoted with its source, the footer requirements (who you are, a postal address, an unsubscribe or opt-out), the next step and a signed receipt id to show a client or auditor. Each call uses one check from your allowance (free daily allowance, no sign-in) and sends nothing to the recipient. Not for transactional emails such as invoices, receipts or password resets. | Read-only |
| verify_receipt | Fetch a Precleared receipt by its id (cc_rcpt_...) to show what was checked, when, and the verdict, with the hashes, Ed25519 signature and public key needed to verify it. Use it when a person or an audit asks for proof of a check. | Read-only |
Change history
- contact_check: input schema changed (+company_name, +recipient_name)
- contact_check: input schema changed
- contact_check: title changed
- contact_check: input schema changed
- contact_check: description changed (+"Is it legal to send" +"this person? Check before the first email to any new lead, prospect or contact who is not already a customer," +"call per address: a compliance check for B2B sales outreach, prospecting and lead lists. Whether it is allowed, or needs consent first, turns on facts you cannot see in the address, such as whether a UK")
- contact_check: annotations changed
- server instructions changed (+"is a cold email compliance check for outbound, sales and prospecting agents. It" +"per recipient: is it legal to send this person" +"email? Call")
- Description changed (registry)
- contact_check: input schema changed (+default_recipient_country)
- verify_receipt: input schema changed
- contact_check: input schema changed
- contact_check: description changed (+"Not needed for transactional emails such as invoices, receipts or password resets." +"what" +"email's")
- server instructions changed (+"is not needed for transactional emails such as invoices, receipts or password resets. It" +"what" +"email's")
- verify_receipt: description changed (+"Fetch" +"its id (cc_rcpt_...) to show what was checked, when, and the verdict," +"the")
- contact_check: input schema changed
- contact_check: description changed (+"or unsolicited" +"one recipient" +"under UK PECR and GDPR, US CAN-SPAM, Canadian CASL, German UWG or French rules. Use it before the first email to a new contact, one call per address.")
- server instructions changed (+"answers one question for outbound agents: may" +"or unsolicited" +"sent to this address? Use contact_check once per recipient before the first email to anyone who is not already a customer, in the UK, US, Canada, Germany or France. It returns a verdict (ok_to_email, consent_needed, blocked or unknown), the rule that decided it")
- Description changed (registry)
- Listed (registry)
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | dev.precleared/contact-check | 12 Oct 2026 | 25 Oct 2026 | 3 |