Search / dev.precleared/contact-check
protogridR0· no sign-inCold email compliance check across 8 countries: per-address verdict, rule cited, signed receipt.
v1.0.4 · active · repository · website · descriptor JSON · versions
{
"mcpServers": {
"contact-check": {
"type": "http",
"url": "https://precleared.dev/mcp",
"headers": {
"Authorization": "Bearer ${CONTACT_CHECK_TOKEN}"
}
}
}
}claude mcp add --transport http contact-check https://precleared.dev/mcp --header "Authorization: Bearer ${CONTACT_CHECK_TOKEN}"[mcp_servers.contact-check]
url = "https://precleared.dev/mcp"
bearer_token_env_var = "CONTACT_CHECK_TOKEN"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"contact-check": {
"type": "remote",
"url": "https://precleared.dev/mcp",
"enabled": true,
"headers": {
"Authorization": "Bearer {env:CONTACT_CHECK_TOKEN}"
}
}
}
}{
"mcpServers": {
"contact-check": {
"type": "http",
"url": "https://precleared.dev/mcp",
"headers": {
"Authorization": "Bearer ${CONTACT_CHECK_TOKEN}"
}
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=contact-check&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vcHJlY2xlYXJlZC5kZXYvbWNwIiwiaGVhZGVycyI6eyJBdXRob3JpemF0aW9uIjoiQmVhcmVyICR7Q09OVEFDVF9DSEVDS19UT0tFTn0ifX0%3D"
}{
"servers": {
"contact-check": {
"type": "http",
"url": "https://precleared.dev/mcp",
"headers": {
"Authorization": "Bearer ${CONTACT_CHECK_TOKEN}"
}
}
}
}{
"mcpServers": {
"contact-check": {
"httpUrl": "https://precleared.dev/mcp",
"headers": {
"Authorization": "Bearer ${CONTACT_CHECK_TOKEN}"
}
}
}
}extensions:
"contact-check":
enabled: true
name: "contact-check"
type: streamable_http
uri: "https://precleared.dev/mcp"
headers:
"Authorization": "Bearer ${CONTACT_CHECK_TOKEN}"
timeout: 300
Placeholders to fill from your own secret store: ${CONTACT_CHECK_TOKEN}. The registry never accepts secret values.
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_length1 tools have descriptions over 1,024 characters, which crowds the contexttools.schemasevery tool has an object input schematools.annotations2 of 2 tools declare readOnlyHint or destructiveHinttools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHinttools.token_costabout 986 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes, stability.rug_pulltool history recorded for 6 of the 7 days neededdeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packagecontact_checkchangeddescription, input schemaIs 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 and French CNIL rules. 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.
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.
contact_checkchangedtitle, description, annotationsmeaning changedCheck 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.
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 and French CNIL rules. 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.
contact_checkchangedoutput schemacontact_checkchangedinput schemaverify_receiptchangedoutput schemacontact_checkchangeddescription, output schemaCheck 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. Returns the verdict, confidence, the rule quoted with its source, the footer wording the email needs, the next step, the facts used and a signed receipt. It does not send anything.
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.
verify_receiptchangeddescription, annotationsmeaning changedReturn a Precleared receipt by id, with its hashes, signature and public key.
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.
contact_checkchangeddescription, input schema, annotationsmeaning changedCheck whether a cold marketing email to this address is allowed (UK, US, Canada, Germany, France). Returns the verdict, the rule quoted, footer wording and a signed receipt.
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. Returns the verdict, confidence, the rule quoted with its source, the footer wording the email needs, the next step, the facts used and a signed receipt. It does not send anything.
Full history: list_changes · trend: quality JSON.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +dns-namespace +website +reachable +uptime-100% +updated-2d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://precleared.dev/mcp streamable-http | none | yes | 100% | 1097 ms | 2025-11-25 | 2026-10-19 |
contact_checkread-only | 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. |
verify_receiptread-only | 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. |
Schemas: list_tools.
{
"name": "dev.precleared/contact-check",
"icons": [
{
"src": "https://precleared.dev/icon.png",
"sizes": [
"512x512"
],
"mimeType": "image/png"
}
],
"title": "Precleared Contact Check",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://precleared.dev/mcp",
"type": "streamable-http",
"headers": [
{
"name": "Authorization",
"isSecret": true,
"description": "Optional. Bearer pc_live_... from https://precleared.dev/get-key, for prepaid packs. Without it, 100 free checks a day over MCP."
}
]
}
],
"version": "1.0.4",
"repository": {
"url": "https://github.com/gabrielaoimevbore-beep/precleared-mcp",
"source": "github"
},
"websiteUrl": "https://precleared.dev",
"description": "Cold email compliance check across 8 countries: per-address verdict, rule cited, signed receipt."
}