dev.certdesk/certdesk

Est-ce que dev.certdesk/certdesk est sûr ?

Au dernier audit MCP Hub, le serveur MCP « dev.certdesk/certdesk » 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 7 outils

• check_certificate≈ 604 tokens

  Check one domain's TLS certificate and return a verdict: status OK | WARN | CRITICAL | UNKNOWN, judged from the certificate chain the server actually serves. Measured from Korean point A (full chain and CRL revocation) plus Korean point B and an overseas point on the Globalping public measurement network (per-point results in measuredFrom; disagreement between points is a WARN). Checks: verification (expired, not yet valid, hostname mismatch, self-signed, untrusted root, missing intermediate, revoked via CRL), days left, renewal point, a newer certificate issued but not deployed (CT logs), the served chain and the issuing CA's incident history. If the server cannot be measured the status is UNKNOWN and CT logs are shown only as an estimate, never as OK. Set detail=true to include the full chain in the text output.

  Paramètres, retour & exemple (5)

  Paramètres

  • port · integer · optionnel
    TLS port (default 443). Implicit TLS: 8443 4443 9443 6443 636 465 993 995 853 5061 3269 8883; STARTTLS: 25 587 (SMTP), 143 (IMAP), 110 (POP3), 389 (LDAP). Or pass domain as host:port
  • detail · boolean · optionnel
    Include the full certificate chain in the text output (default false)
  • domain · string · requis
    Domain name, e.g. example.com
  • critDays · integer · optionnel
    Days before expiry that count as CRITICAL "expiring soon" (default 15; must be < warnDays)
  • warnDays · integer · optionnel
    Days before expiry that count as WARN (default 30; the default shrinks for short-lived certificates)

  Exemple d'appel

  {"name": "check_certificate", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"domain": "texte", "status": "OK", "reasons": [], "headline": "texte"}}

• check_dns≈ 117 tokens

  DNS and hosting facts for a domain: nameservers with DNS provider, A/AAAA with IP owner (ASN), CNAME, MX, CAA (which CAs may issue), SPF/DMARC, DNSSEC, registrar and domain expiry (RDAP).

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis
    Domain name, e.g. example.com

  Exemple d'appel

  {"name": "check_dns", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• check_dns_propagation≈ 180 tokens

  Compare answers for one DNS record across resolvers: the authoritative nameservers, Korean ISPs (KT, SK Broadband, LG U+) and public resolvers (Cloudflare, Google, Quad9, OpenDNS), measured from a Korean network. Use it to confirm a TXT/CNAME for certificate domain validation (e.g. _acme-challenge) has propagated.

  Paramètres, retour & exemple (2)

  Paramètres

  • name · string · requis
    Record name, e.g. _acme-challenge.example.com
  • type · string · requis · A | AAAA | CNAME | TXT | MX | NS | CAA | SOA

  Exemple d'appel

  {"name": "check_dns_propagation", "arguments": {"name": "texte", "type": "A"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• check_expiry≈ 436 tokens

  Verdict for up to 5 domains at once: status OK | WARN | CRITICAL | UNKNOWN per domain combining the served certificate (verification, days left, null when the server cannot be measured) and domain registration expiry (RDAP), plus Korean alert lines. Use this for inventories, CI gates (fail unless status is OK) and periodic checks.

  Paramètres, retour & exemple (3)

  Paramètres

  • domains · array · requis
    Domain names
  • critDays · integer · optionnel
    Days before expiry that count as CRITICAL "expiring soon" (default 15; must be < warnDays)
  • warnDays · integer · optionnel
    Days before expiry that count as WARN (default 30; the default shrinks for short-lived certificates)

  Exemple d'appel

  {"name": "check_expiry", "arguments": {"domains": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"results": [], "checkedAt": "texte"}}

• check_security≈ 155 tokens

  Security posture check of a web server (no port scanning): TLS protocol support (legacy 1.0/1.1 detection via a Korean network probe), security headers (HSTS/CSP/X-Content-Type-Options/anti-clickjacking/Referrer-Policy), HTTP→HTTPS redirect, and certificate key/signature strength. Returns per-item pass/warn/fail and an overall grade.

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis
    Domain name, e.g. example.com

  Exemple d'appel

  {"name": "check_security", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• explain_tls_error≈ 140 tokens

  Explain a TLS/SSL certificate error message from a browser, curl/OpenSSL, Java, Python, Node.js, Go or .NET: likely causes, fixes, and links to step-by-step guides (Korean). Works offline from a curated knowledge base.

  Paramètres, retour & exemple (1)

  Paramètres

  • error · string · requis
    Full error text, e.g. "PKIX path building failed" or "NET::ERR_CERT_DATE_INVALID"

  Exemple d'appel

  {"name": "explain_tls_error", "arguments": {"error": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• watch_expiry≈ 568 tokens

  Subscribe an email address to free daily expiry monitoring of up to 5 domains (certificate, domain registration and security grade) with email alerts, plus an optional Slack/Discord/Telegram/webhook channel. Also alerts when Certificate Transparency logs show a new certificate for a domain from a CA not seen before (possible unauthorized issuance). Double opt-in: a confirmation email is sent and monitoring starts only after the recipient clicks the link; one confirmation email per address per 24 hours. Use only an address the user owns and explicitly asked to use.

  Paramètres, retour & exemple (6)

  Paramètres

  • email · string · requis
    Email address that will receive the alerts
  • domains · array · requis
    Domain names to monitor (host or host:port). For paid certificates you may append the contract (subscription) end date and the DCV method, e.g. "shop.example.com 2027-05-01 email". Contract expiry is alerted with the same thresholds and email DCV gets a reminder (email DCV ends 2028-03-15, CA/B Forum SC-090). A trailing "45/20" sets per-domain WARN/CRITICAL days.
  • webhook · string · optionnel
    Optional alert channel URL. Alerts are also posted there after confirmation. Accepts a Slack or Discord incoming-webhook URL, a Telegram URL https://api.telegram.org/bot<TOKEN>/sendMessage?chat_id=<CHAT_ID>, or any public https endpoint (receives JSON POST, version 1). It is a secret; only pass a URL the user gave you.
  • critDays · integer · optionnel
    Days before expiry that count as CRITICAL "expiring soon" (default 15; must be < warnDays)
  • warnDays · integer · optionnel
    Days before expiry that count as WARN (default 30; the default shrinks for short-lived certificates)
  • slackWebhook · string · optionnel
    Deprecated alias of webhook that accepts only Slack Incoming Webhook URLs (https://hooks.slack.com/services/...).

  Exemple d'appel

  {"name": "watch_expiry", "arguments": {"email": "texte", "domains": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

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://certdesk.dev/mcp