Precleared Contact Check

What Precleared Contact Check does

Precleared Contact Check MCP server provides decision support for cold marketing email. It covers the UK through PECR and UK GDPR, the United States through CAN-SPAM, Canada through CASL, Germany through UWG, and France. The service is intended to sit after a workflow discovers a contact and before an outreach tool sends the first message.

The main check is contact-specific. It considers the recipient email address or domain, the sender’s country, the proposed pitch, and how the address was obtained. The sender country input supports GB or US. Results classify the contact as ok_to_email, consent_needed, blocked, or unknown, along with a confidence value and the facts used in the decision.

How it works

The contact_check tool sends the supplied facts to the hosted Precleared API, or to that API through the local repository server. Its response includes the applicable rule, the source supporting that rule, a next action, and footer_text. The footer field describes required content such as sender identification, a postal address, or a way to stop future emails; it is guidance about what the footer must contain, not ready-to-paste copy.

Each check can produce a signed receipt. The receipt records the question, supplied facts, time, and resulting answer. The verify_receipt tool accepts a receipt ID and returns its hashes, Ed25519 signature, public key, key version, and verification URL. Receipts can also be checked through the public receipt page or with the published public key.

Setup and configuration

The hosted MCP endpoint is https://precleared.dev/mcp and uses streamable HTTP. It can be added to supported clients with a URL, or connected through mcp-remote. Claude Code can register it with an HTTP transport command. Cursor and VS Code have installation links documented by the project.

For local use, Node.js 18 or later can run the repository with npx, or the project can be built and run in Docker. The local process exposes the same two tools and calls the public REST API. Configure PRECLEARED_API_KEY when using a key, PRECLEARED_API_BASE to change the API base URL, and PRECLEARED_TIMEOUT_MS to change the request timeout. The latter defaults to 30000 milliseconds. The API key is optional, and authorization can be supplied through a bearer header or X-API-Key when connecting directly.

Tools and capabilities

• contact_check: evaluates a proposed cold-email contact and returns a verdict, confidence, cited rule, footer requirements, next step, facts, and signed receipt.
• verify_receipt: retrieves receipt data, hashes, the Ed25519 signature, and public key for verification.
• Hosted MCP access, local stdio execution, Docker execution, and direct REST access are documented by the project.

Limitations and notes

Precleared Contact Check is intended for cold marketing email and is not needed for invoices, receipts, or other transactional email. Its result is decision support with sources, not legal advice. The local server does not store data locally or send messages to recipients, but it does forward check requests to the configured Precleared API.

Hosted access allows 100 checks per day without a key, while the REST API used by the local server allows 10 per day per network without one. A free key and paid packs are available through the project’s service. The repository includes tests that use a fake local API and do not require network access.