Precleared Contact Check
REMOTE · PRECLEARED.DEV
Cold email compliance check, 12 countries: per-address verdict, rule cited, signed receipt.
Available components
Last scanned (17 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1716 tokens (~429/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “contact_check” rewrote its description, which is the text the model reads security
- Schema quality: 1382 → 1716 ▼ functional
- Tool coverage: 67% → 50% ▼ functional
- New tool “suppress_contact” functional
- “contact_check” added an optional parameter “email” cosmetic
- 2 Nov 26 0
- Tool “contact_check” rewrote its description, which is the text the model reads security
- “contact_check” reworded the description of “sender_country” cosmetic
- 1 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 100% → 67% ▼ functional
- Schema quality: 616 → 447 ▲ functional
- New tool “link_account” functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://precleared.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=precleared.dev | CN=WE1,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | feb2822ae3f434260ed04db96b1f8831 |
| SANs: precleared.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of precleared.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| precleared.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://precleared.dev/mcp | Verified | 200 | |
| http (plaintext) | http://precleared.dev/mcp | HTTPS enforced | 301 | https://precleared.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
contact_check Cold email compliance check ~903
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, the Dutch Telecommunicatiewet, Spain's LSSI, Italy's Privacy Code, Latvia's Information Society Services Law and the UAE's PDPL. 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 charged call uses one check from your allowance (free daily allowance, no sign-in); unknown-country answers and one qualifying re-check within a day are free, up to a combined limit of 50 a day. Nothing is sent to the recipient. Not for transactional emails such as invoices, receipts or password resets. To check the email itself, send the draft as email ({ subject, body, from_name, from_email }); the answer then gains email_check, saying whether the footer has an opt-out, the sender's identity and, where the rule needs one, a postal address. The draft is not stored. Addresses on the key's opt-out list (see suppress_contact) come back blocked and free.
| Name | Type | Req | Description |
|---|---|---|---|
| address_source | string | – | 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 t… |
| company_name | string | – | The recipient's company or organisation name if you know it, for example from your CRM. For UK recipients it is used to search Companies House when the domain alone does not find the company. A compa… |
| company_number | string | – | UK company number if known (8 characters), so the register can confirm the company. |
| default_recipient_country | string | – | Two-letter country code to use only when the recipient's country can't be worked out from recipient_country, the domain, company records or the company's website, for example US if all your prospects… |
| object | – | The draft email, if you want the answer to say whether its footer meets the rule for the recipient's country. The body is not stored. | |
| existing_customer | boolean | – | True if the recipient has bought from you before. Default false. |
| pitch | string | – | What the email offers, in a few words, for example 'bookkeeping software for dental practices'. Used to judge relevance to the recipient's role. |
| pitch_relevant | boolean | – | True if the pitch relates to the recipient's job or business, false if it does not. |
| recipient_country | string | – | Two-letter country code of the recipient if known, for example GB or DE. Otherwise it is worked out from the domain, company records and the company's website. |
| recipient_domain | string | – | The recipient's domain when you have no email address, for example acme.co.uk. |
| recipient_email | string | – | The recipient's email address. Give this or recipient_domain. |
| recipient_name | string | – | The recipient's full name if you know it, for example Jane Smith. For UK recipients it is matched against a company's current officers at Companies House. Precleared does not store it. |
| sender_country | string | – | Country the sending business is based in: GB, US, AE (United Arab Emirates) or CA (Canada). Canadian senders must also meet CASL. Not the recipient's country. Default GB. |
| suppressed | boolean | – | True if the recipient is on your own do-not-contact list. |
| Name | Type | Req | Description |
|---|---|---|---|
| charged | boolean | – | – |
| confidence | string | – | high, medium or low. |
| disclaimer | string | – | Fixed disclaimer line. |
| email_check | object | – | Present when you sent email: whether the draft's footer has what the rule needs. |
| facts | object | – | Facts gathered about the recipient. |
| footer_text | string|null | – | What the email's footer must include, if the rule sets requirements. |
| free_recheck_of | string | – | – |
| held_because | object | – | – |
| next_step | string|null | – | What to do next. |
| possible_company | object | – | – |
| reasons | array | – | The rule that matched, with its text and source, then any notes. |
| receipt | object | – | Signed receipt for this check. |
| rules_applied | array | – | Rule keys used. |
| rules_version | string | – | Version of the rule set used. |
| usage | object | – | Allowance left for the caller. |
| verdict | string | yes | The answer for this recipient. |
No examples provided.
link_account Sign in to Precleared ~83
Links this connection to the person's own Precleared key, so checks use their own free allowance, 14-day trial and plan instead of the shared free allowance. Use it when the person asks to sign in to or connect Precleared, or when contact_check says the free checks have run out. If they aren't signed in, Claude will ask them to sign in.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
suppress_contact Add to or remove from the opt-out list ~163
Records that a person asked not to be emailed, on this Precleared key's opt-out list, so every agent and tool using the key gets blocked for that address from contact_check. Use it as soon as someone replies stop, unsubscribes, bounces or complains. Give email or domain; set remove to true only when the person asks to be emailed again. Needs a Precleared key (a free one is fine). Never charged. The address is kept only as a hash and a masked copy.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | A whole domain, such as acme.co.uk. |
| string | – | The address. | |
| reason | string | – | Default opted_out. |
| remove | boolean | – | True to take the entry off the list. |
No output schema declared.
No examples provided.
verify_receipt Verify receipt ~89
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 | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Receipt id, such as cc_rcpt_0123456789ABCDEF. |
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string|null | – | Signature algorithm. |
| confidence | string|null | – | Confidence given. |
| created_at | string|null | – | When the check was made. |
| id | string | yes | Receipt id. |
| key_version | string|null | – | Signing key version. |
| public_key | string|null | – | Public key, base64 SPKI DER. |
| recipient_domain | string|null | – | Recipient domain. |
| recipient_email_masked | string|null | – | Masked recipient address. |
| request_hash | string|null | – | SHA-256 of the request. |
| response_hash | string|null | – | SHA-256 of the response. |
| rules_applied | – | – | Rule keys used. |
| rules_version | string|null | – | Rule set version. |
| sender_country | string|null | – | Sender country. |
| signature | string|null | – | Ed25519 signature, base64. |
| verdict | string|null | – | Verdict given. |
No examples provided.
How do I install the Precleared Contact Check MCP server?
Precleared Contact Check is a hosted endpoint at https://precleared.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · precleared.dev
claude mcp add --transport http dev-precleared-contact-check 'https://precleared.dev/mcp'
What is the Precleared Contact Check MCP server?
Precleared Contact Check is an MCP server listed in the public MCP registry as dev.precleared/contact-check. Cold email compliance check, 12 countries: per-address verdict, rule cited, signed receipt. This page covers its hosted endpoint (https://precleared.dev/mcp).
Is the Precleared Contact Check MCP server safe to use?
Precleared Contact Check scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Precleared Contact Check MCP server expose?
Precleared Contact Check exposes 4 tools: contact_check, verify_receipt, suppress_contact, link_account. Their descriptions and schemas cost roughly 1,238 tokens of context every time the server is loaded.
Does the Precleared Contact Check MCP server require authentication?
No. We connected to Precleared Contact Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Precleared Contact Check MCP server still maintained?
Precleared Contact Check is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Precleared Contact Check MCP server?
VerifyMCP ran 13 checks on Precleared Contact Check, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.