Precleared Contact Check
Server Details
Cold email compliance check for outreach agents: GDPR, PECR, CAN-SPAM, CASL verdict, signed receipt.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- gabrielaoimevbore-beep/precleared-mcp
- GitHub Stars
- 0
TDQS
Score is being calculated.
Available Tools
2 toolscontact_checkContact CheckInspect
Check whether a cold or unsolicited marketing email to one recipient is allowed 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. Not needed for transactional emails such as invoices, receipts or password resets. Returns the verdict, confidence, the rule quoted with its source, what the email's footer must include, the next step and the facts used. Each check uses one check from your allowance and is saved as a signed receipt. It does not send anything.
| Name | Required | Description | Default |
|---|---|---|---|
| pitch | No | What the email offers, in a few words, for example 'bookkeeping software for dental practices'. Used to judge relevance to the recipient's role. | |
| suppressed | No | True if the recipient is on your own do-not-contact list. | |
| address_source | No | Where the address came from: published (on their website, profile or a directory), bought (a purchased list), scraped (collected by a tool), given (the person gave it to you) or unknown. It affects the verdict, so do not assume published. | |
| company_number | No | UK company number if known (8 characters), so the register can confirm the company. | |
| pitch_relevant | No | True if the pitch relates to the recipient's job or business, false if it does not. | |
| sender_country | No | Country the sending business is based in, GB or US. Not the recipient's country. Default GB. | |
| recipient_email | No | The recipient's email address. Give this or recipient_domain. | |
| recipient_domain | No | The recipient's domain when you have no email address, for example acme.co.uk. | |
| existing_customer | No | True if the recipient has bought from you before. Default false. | |
| recipient_country | No | Two-letter country code of the recipient if known, for example GB or DE. Otherwise it is worked out from the domain and company records. |
Output Schema
| Name | Required | Description |
|---|---|---|
| facts | No | Facts gathered about the recipient. |
| usage | No | Allowance left for the caller. |
| reasons | No | The rule that matched, with its text and source, then any notes. |
| receipt | No | Signed receipt for this check. |
| verdict | Yes | The answer for this recipient. |
| next_step | No | What to do next. |
| confidence | No | high, medium or low. |
| disclaimer | No | Fixed disclaimer line. |
| footer_text | No | What the email's footer must include, if the rule sets requirements. |
| rules_applied | No | Rule keys used. |
| rules_version | No | Version of the rule set used. |
verify_receiptVerify receiptRead-onlyIdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Receipt id, such as cc_rcpt_0123456789ABCDEF. |
Output Schema
| Name | Required | Description |
|---|---|---|
| id | Yes | Receipt id. |
| verdict | No | Verdict given. |
| algorithm | No | Signature algorithm. |
| signature | No | Ed25519 signature, base64. |
| confidence | No | Confidence given. |
| created_at | No | When the check was made. |
| public_key | No | Public key, base64 SPKI DER. |
| key_version | No | Signing key version. |
| request_hash | No | SHA-256 of the request. |
| response_hash | No | SHA-256 of the response. |
| rules_applied | No | Rule keys used. |
| rules_version | No | Rule set version. |
| sender_country | No | Sender country. |
| recipient_domain | No | Recipient domain. |
| recipient_email_masked | No | Masked recipient address. |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- Changed
contact_check1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "confidence": { + "description": "high, medium or low.", + "type": "string" + }, + "disclaimer": { + "description": "Fixed disclaimer line.", + "type": "string" + }, + "facts": { + "additionalProperties": {}, + "description": "Facts gathered about the recipient.", + "properties": {}, + "type": "object" + }, + "footer_text": { + "description": "What the email's footer must include, if the rule sets requirements.", + "type": [ + "string", + "null" + ] + }, + "next_step": { + "description": "What to do next.", + "type": [ + "string", + "null" + ] + }, + "reasons": { + "description": "The rule that matched, with its text and source, then any notes.", + "items": { + "additionalProperties": {}, + "properties": {}, + "type": "object" + }, + "type": "array" + }, + "receipt": { + "additionalProperties": {}, + "description": "Signed receipt for this check.", + "properties": { + "id": { + "type": "string" + }, + "verify_url": { + "type": "string" + } + }, + "type": "object" + }, + "rules_applied": { + "description": "Rule keys used.", + "items": { + "type": "string" + }, + "type": "array" + }, + "rules_version": { + "description": "Version of the rule set used.", + "type": "string" + }, + "usage": { + "additionalProperties": {}, + "description": "Allowance left for the caller.", + "properties": { + "credits_remaining": { + "type": "number" + }, + "free_remaining_today": { + "type": "number" + } + }, + "type": "object" + }, + "verdict": { + "description": "The answer for this recipient.", + "enum": [ + "ok_to_email", + "consent_needed", + "blocked", + "unknown" + ], + "type": "string" + } + }, + "required": [ + "verdict" + ], + "type": "object" +}
- Changed
verify_receipt1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "algorithm": { + "description": "Signature algorithm.", + "type": [ + "string", + "null" + ] + }, + "confidence": { + "description": "Confidence given.", + "type": [ + "string", + "null" + ] + }, + "created_at": { + "description": "When the check was made.", + "type": [ + "string", + "null" + ] + }, + "id": { + "description": "Receipt id.", + "type": "string" + }, + "key_version": { + "description": "Signing key version.", + "type": [ + "string", + "null" + ] + }, + "public_key": { + "description": "Public key, base64 SPKI DER.", + "type": [ + "string", + "null" + ] + }, + "recipient_domain": { + "description": "Recipient domain.", + "type": [ + "string", + "null" + ] + }, + "recipient_email_masked": { + "description": "Masked recipient address.", + "type": [ + "string", + "null" + ] + }, + "request_hash": { + "description": "SHA-256 of the request.", + "type": [ + "string", + "null" + ] + }, + "response_hash": { + "description": "SHA-256 of the response.", + "type": [ + "string", + "null" + ] + }, + "rules_applied": { + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ], + "description": "Rule keys used." + }, + "rules_version": { + "description": "Rule set version.", + "type": [ + "string", + "null" + ] + }, + "sender_country": { + "description": "Sender country.", + "type": [ + "string", + "null" + ] + }, + "signature": { + "description": "Ed25519 signature, base64.", + "type": [ + "string", + "null" + ] + }, + "verdict": { + "description": "Verdict given.", + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "id" + ], + "type": "object" +}
1 tool update
- Changed
contact_check10 fields changed- changed
Input schema / properties / address_source / descriptionPrevious value: -"Where the address came from. Default published."New value: +"Where the address came from: published (on their website, profile or a directory), bought (a purchased list), scraped (collected by a tool), given (the person gave it to you) or unknown. It affects the verdict, so do not assume published." - changed
Input schema / properties / company_number / descriptionPrevious value: -"UK company number, if known. Speeds up UK checks."New value: +"UK company number if known (8 characters), so the register can confirm the company." - changed
Input schema / properties / existing_customer / descriptionPrevious value: -"Whether the recipient is already a customer. Default false."New value: +"True if the recipient has bought from you before. Default false." - changed
Input schema / properties / pitch / descriptionPrevious value: -"A short description of what the email offers."New value: +"What the email offers, in a few words, for example 'bookkeeping software for dental practices'. Used to judge relevance to the recipient's role." - changed
Input schema / properties / pitch_relevant / descriptionPrevious value: -"Whether the pitch relates to the recipient's role or business."New value: +"True if the pitch relates to the recipient's job or business, false if it does not." - changed
Input schema / properties / recipient_country / descriptionPrevious value: -"ISO 3166 two-letter country of the recipient, if known."New value: +"Two-letter country code of the recipient if known, for example GB or DE. Otherwise it is worked out from the domain and company records." - changed
Input schema / properties / recipient_domain / descriptionPrevious value: -"Recipient domain, used when there is no email address."New value: +"The recipient's domain when you have no email address, for example acme.co.uk." - changed
Input schema / properties / recipient_email / descriptionPrevious value: -"Recipient email address. Give this or recipient_domain."New value: +"The recipient's email address. Give this or recipient_domain." - changed
Input schema / properties / sender_country / descriptionPrevious value: -"Where the sender is based. GB or US. Default GB."New value: +"Country the sending business is based in, GB or US. Not the recipient's country. Default GB." - changed
Input schema / properties / suppressed / descriptionPrevious value: -"Set true if the recipient is on your own suppression list."New value: +"True if the recipient is on your own do-not-contact list."
2 tool updates
- First observed
contact_check - First observed
verify_receipt
Publisher details
- Operator
- Precleared · Publisher source
- Operator website
- https://precleared.dev
- Vendor relationship
- First-party
- Documentation
- https://precleared.dev/docs · Publisher source
- Trust center
- Not available
- Restrictions
- Free without a key: 100 checks a day over MCP, shared by everyone on the same IP address. A free key gives you your own 100 a day over MCP, or 25 over the REST API. A pack is £39 for 2,000 checks, which never expire. It covers recipients in the UK, US, Canada, Germany and France, and the sending business must be based in the UK or US. · Publisher source
Related MCP Connectors
B2B outreach CRM for AI agents: contacts, verification, approved campaigns, replies, follow-ups.
1- WarmerlyOAuthcom.warmerly
Cold email outreach: find leads, launch campaigns, fix deliverability, answer replies.
AI-powered email outreach platform — send campaigns with deliverability tracking.
AI-agent outreach: cold email, warmup, LinkedIn, Instagram, WhatsApp, verification, 200M leads
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides rules, checklists, and audits for cold outreach deliverability across email, LinkedIn, Instagram, and X, helping ensure messages land in inboxes rather than spam folders.640 npmMIT
- FlicenseAqualityDmaintenanceEMEA sales + employment compliance for AI agents across 7 countries (UK, Germany, France, Spain, Italy, Netherlands, Sweden). GDPR, IR35, CNIL, B2B opt-out rules, cultural buyer psychology. Built by an ex-Deel ($12B) compliance + sales operator.7-
- AlicenseNot gradedqualityBmaintenanceEnables agents to find leads, read buying signals, write and send email and LinkedIn outreach, handle replies, and report results, with built-in safety gates, approvals, limits, and compliance controls.3Apache 2.0
- AlicenseAqualityDmaintenanceProvides AI agents with tools for structuring and auditing cold outreach messages, building follow-up sequences, handling replies, and detecting red flags.739 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.