accueil / serveurs / Communication / com.domaincanary/mcp
com.domaincanary/mcp
serveur MCP (Model Context Protocol) · domaincanary 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que com.domaincanary/mcp est sûr ?
Au dernier audit MCP Hub, le serveur MCP « com.domaincanary/mcp » 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 4 outils
- analyze_report≈ 1416 tokens
Use this when someone has a DMARC aggregate report and wants to know which senders passed and which failed. The report is the XML, .gz or .zip file that receivers such as Google and Yahoo email to the address in a domain's rua tag. In ChatGPT, pass the uploaded file. Elsewhere, pass the report XML as text. Returns totals per report and each sending IP address with its SPF, DKIM and DMARC results. The result gives a next step for the report's domain and a link to a live check of that domain's DNS records. Nothing from the report is stored.
Paramètres, retour & exemple (2)
Paramètresfile· object · optionnel
The report file the user uploaded in ChatGPT: the .xml, .xml.gz or .zip a mailbox provider emailed them.report_xml· string · optionnel
The report XML as text, from <feedback> to </feedback>. Use this when there is no uploaded file, or when the user pasted the XML.
Exemple d'appel{"name": "analyze_report", "arguments": {"file": {}, "report_xml": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"reports": [], "next_steps": [], "analyzer_url": "texte", "external_data": {}, "reports_omitted": 1, "skipped_payloads": 1, "record_limit_reached": true}} - build_spf≈ 1015 tokens
Use this when someone lists the services that send their email and wants the SPF record to publish, or wants a sender added to the SPF record they already have. Takes provider names such as Google Workspace or Mailchimp, include terms such as include:spf.example.com, or IP addresses, and returns one merged record with its count of DNS lookups against the limit of ten. Pass the domain when you know it, so the result includes the senders already in its published record.
Paramètres, retour & exemple (5)
Paramètresall· string · optionnel · ~all | -all
How the record ends. A new record ends in ~all unless you pass -all. A record the domain already publishes keeps its own ending unless you pass one.ip4· array · optionnel
IPv4 addresses or ranges that send this domain's mail directly, such as 192.0.2.10 or 192.0.2.0/24.ip6· array · optionnel
IPv6 addresses or ranges that send this domain's mail directly, such as 2001:db8::1 or 2001:db8::/32.domain· string · optionnel
The domain the record is for. When given, the SPF record it publishes today is read and the senders are added to it, so nothing already in it is lost.senders· array · requis
The platforms that send this domain's mail: provider names such as Google Workspace or Mailchimp, or include terms such as include:spf.example.com.
Exemple d'appel{"name": "build_spf", "arguments": {"senders": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "added": [], "after": "texte", "domain": "texte", "lookups": 1, "outcome": "built", "skipped": [], "findings": [], "published": true, "no_include": [], "over_limit": true, "unrecognised": 1}} - check_domain≈ 1035 tokens
Use this when someone asks whether a domain's email authentication is set up correctly, why mail from a domain fails DMARC, SPF or DKIM, or which DNS records to publish for it. Reads the domain's live DMARC, SPF and DKIM records and returns what is wrong with each, plus the records to add or change. Pass a DKIM selector when you know it. Without one, common selectors are tried. Takes a domain name only, not a mailbox address or an IP address.
Paramètres, retour & exemple (2)
Paramètresdomain· string · requis
The domain to check, such as example.com. A URL is cut down to its host.selector· string · optionnel
The DKIM selector, the s= value in a DKIM-Signature header. Leave it out to try common ones.
Exemple d'appel{"name": "check_domain", "arguments": {"domain": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"spf": {}, "url": "texte", "dkim": {}, "dmarc": {}, "domain": "texte", "verdict": "clean", "external_data": {}, "records_to_publish": []}} - explain_bounce≈ 464 tokens
Use this when someone pastes a bounce message, an SMTP reply such as 550 5.7.26, or an Authentication-Results header and asks what it means or how to fix it. Returns what the receiving server refused, what to change, when it clears, and the page that explains it. Works from the pasted text alone and reads no DNS records.
Paramètres, retour & exemple (1)
Paramètrestext· string · requis
The bounce message, the SMTP reply or the Authentication-Results line, as pasted. When the bounce runs past 4,000 characters, pass the lines with the error code and the reason.
Exemple d'appel{"name": "explain_bounce", "arguments": {"text": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"faq": [], "code": "texte", "page": {}, "change": "texte", "clears": "texte", "matched": true, "meaning": "texte", "related": []}}
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é ».