dev.precleared/contact-check

Est-ce que dev.precleared/contact-check est sûr ?

Au dernier audit MCP Hub, le serveur MCP « dev.precleared/contact-check » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 2 outils

• contact_check≈ 1312 tokens

  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.

  Paramètres, retour & exemple (11)

  Paramètres

  • pitch · string · optionnel
    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 · boolean · optionnel
    True if the recipient is on your own do-not-contact list.
  • address_source · string · optionnel · published | bought | scraped | given | unknown
    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. Default unknown.
  • company_number · string · optionnel
    UK company number if known (8 characters), so the register can confirm the company.
  • pitch_relevant · boolean · optionnel
    True if the pitch relates to the recipient's job or business, false if it does not.
  • sender_country · string · optionnel · GB | US
    Country the sending business is based in, GB or US. Not the recipient's country. Default GB.
  • recipient_email · string · optionnel
    The recipient's email address. Give this or recipient_domain.
  • recipient_domain · string · optionnel
    The recipient's domain when you have no email address, for example acme.co.uk.
  • existing_customer · boolean · optionnel
    True if the recipient has bought from you before. Default false.
  • recipient_country · string · optionnel
    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.
  • default_recipient_country · string · optionnel
    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 are in the US. recipient_country always wins.

  Exemple d'appel

  {"name": "contact_check", "arguments": {"pitch": "texte", "suppressed": true, "address_source": "published", "company_number": "texte", "pitch_relevant": true, "sender_country": "GB"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"facts": {}, "usage": {}, "reasons": [], "receipt": {}, "verdict": "ok_to_email", "next_step": "texte", "confidence": "texte", "disclaimer": "texte", "footer_text": "texte", "rules_applied": [], "rules_version": "texte"}}

• verify_receipt≈ 529 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Receipt id, such as cc_rcpt_0123456789ABCDEF.

  Exemple d'appel

  {"name": "verify_receipt", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "verdict": "texte", "algorithm": "texte", "signature": "texte", "confidence": "texte", "created_at": "texte", "public_key": "texte", "key_version": "texte", "request_hash": "texte", "response_hash": "texte", "rules_applied": "texte", "rules_version": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://precleared.dev/mcp