accueil / serveurs / Données & BDD / ai.certscore/mcp-light
ai.certscore/mcp-light
serveur MCP (Model Context Protocol) · certscore 0.2.30
Aucun comportement malveillant détecté au test comportemental.
Est-ce que ai.certscore/mcp-light est sûr ?
Au dernier audit MCP Hub, le serveur MCP « ai.certscore/mcp-light » est classé « Vérifié ». Aucun comportement malveillant détecté au test comportemental. 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
- certscore_get_report_evidence_page≈ 1387 tokens
For a focused question, use section=cmp, cms, consent, gpc, policy, tracking, transport, forms or accessibility. This returns selected retained report sections plus shared scan, score, findings and coverage context. CMP includes all 13 criteria with their assessment results and retained comparisons; CMS includes platform/version evidence and existing advisories. Policy also includes retained privacy-choice controls, unverified link candidates and notice passages; California-focused reports include their shared privacy section. detailedEvidence carries shared display wording, counts and cross-links; these audit rows are not additional findings. Preserve section on cursor continuation; unselected or not-returned fields are not evidence of absence. Use workpaper=tracking separately for the starting-page tracking inventory, privacy choices/notices and GPC evidence, with JSON and CSV downloads. Never combine section and workpaper. The workpaper selector also applies to every continuation request. Otherwise retrieve scan report display content as paginated JSON, without internal diagnostic JSON downloads. The response also offers a single-file full JSON download; private JSON download links expire after five minutes and need no OAuth header; use pagination if your host blocks file downloads. Repeated display records use reportContentRef JSON Pointers. Includes evidence tables, full-site page and resource inventories, all retained additional-page form fields, form snapshot download references, and retained limitations. Snapshot images are downloaded separately from the returned URLs, with OAuth bearer authentication for workspace scans. Available on OAuth and Light. Start with scanId; follow pagination.nextCursor until complete. Pages share a snapshot; restart if it changes. Each entry has a JSON Pointer path and value; oversized strings use numbered parts. Export completion is not complete observation coverage. Use the concise scan bundle for summaries; use this tool for exhaustive report evidence. No new scan is created.
Paramètres, retour & exemple (4)
Paramètrescursor· string · optionnelscanId· string · requissection· string · optionnel · consent | gpc | policy | tracking | transport | forms | accessibility | cmpworkpaper· string · optionnel
Exemple d'appel{"name": "certscore_get_report_evidence_page", "arguments": {"scanId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"type": "texte", "scanId": "texte", "entries": [], "section": "consent", "version": 1, "coverage": {}, "download": {}, "snapshot": "texte", "reportUrl": "texte", "selection": {}, "workpaper": "texte", "pagination": {}}} - certscore_get_scan_bundle≈ 15544 tokens
Main answer for a completed or completed-limited scan: canonical findings, next steps, supporting evidence, score, date/region, coverage and report URL. An existing scanId is enough; no new scan is created. The evidence index describes response delivery, never evidence absence. Optional next actions lead to deeper report tables, tracking workpapers and JSON/CSV exports. Use detail=evidence for request examples and policy candidates, including scans with no findings; detail=full adds bounded retained context. Preserve returned/total counts and omission metadata. Accept/Reject execution succeeded means a completed click and bounded observation; succeeded_with_confirmation additionally verifies the consent decision. Retained after-click facts remain distinct from registered decisions. Absent or failed capture remains explicitly limited. Use canonical findings for scoring effects. A later missing finding does not prove a fix. Results are automated public-web observations, not legal advice, certification, or a compliance determination.
Paramètres, retour & exemple (5)
Paramètresdetail· string · optionnel · summary | findings | evidence | full
Response detail. Defaults to summary; evidence and full opt into heavier retained context.scanId· string · requis
Stable CertScore scan ID.maxBytes· integer · optionnel
Requested serialized structured response budget in bytes. The full profile defaults to 50000. MCP Light defaults to and applies a transport-safe 25000-byte ceiling; larger Light requests are clamped and reported in response metadata.maxFindings· integer · optionnel
Maximum compact findings to return. Defaults to 5 for summary and 20 otherwise.maxPreConsentRows· integer · optionnel
Maximum compact pre-consent inventory rows to return. Defaults to 20.
Exemple d'appel{"name": "certscore_get_scan_bundle", "arguments": {"scanId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "noGo": "texte", "type": "texte", "error": "texte", "links": {}, "score": "texte", "detail": "summary", "domain": "texte", "scanId": "texte", "status": "queued", "timing": {}, "summary": {}}} - certscore_get_scan_status≈ 9195 tokens
Returns lifecycle status for a stable CertScore scanId. Active responses include phase, heartbeat, estimated progress, retryAfterSeconds, and sometimes a bounded preliminary preConsentPreview. Terminal responses include completion status, CertScore score and risk metadata when available, coverage, persisted execution region and timestamps, report URL, and a next-action field. Preliminary observations are distinct from completed findings.
Paramètres, retour & exemple (1)
ParamètresscanId· string · requis
Stable CertScore scan ID returned by certscore_scan_site.
Exemple d'appel{"name": "certscore_get_scan_status", "arguments": {"scanId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "noGo": {}, "type": "certscore_scan_job", "error": "texte", "jobId": "texte", "links": {}, "phase": "texte", "score": "texte", "domain": "texte", "scanId": "texte", "status": "queued", "scan_id": "texte"}} - certscore_scan_site≈ 9627 tokens
Use for a user-requested website launch review, vendor assessment, cookie/tracker inventory, consent/GPC investigation or privacy-policy review. A public URL or domain is enough. Creates a privacy scan or reuses an eligible recent completed scan; default freshness=latest saves new-scan quota. Use refresh only for an explicitly requested fresh scan or post-fix recheck. Retain scanId, poll certscore_get_scan_status only while active at retryAfterSeconds, then read certscore_get_scan_bundle. A preliminary preConsentPreview is not final findings or totals. Coverage includes pre-consent storage, trackers, consent and CMP signals, privacy-policy disclosures, transport security and GDPR/ePrivacy or CCPA/CPRA review signals. Results are automated observations, not legal advice, certification, or a compliance determination. https://certscore.ai/developers/mcp.
Paramètres, retour & exemple (4)
Paramètresurl· string · requis
Public URL or domain to scan.scanFrom· string · optionnel · eu_de | eu_ie | california
Optional execution region for a newly queued scan: eu_de, eu_ie, california, or the service default when omitted.freshness· string · optionnel · latest | refresh
Scan freshness policy. latest allows eligible recent completed-result reuse when available; refresh requests a new scan. Defaults to latest.taskContext· object · optionnel
Optional caller-declared purpose and integration ID/version for usage research. Only include questionSummary when the user knowingly agrees to share a brief non-sensitive question for product improvement; label user_wording or agent_paraphrase. Never include chat history, personal/account details, secrets or URLs. Omission does not affect scanning.
Exemple d'appel{"name": "certscore_scan_site", "arguments": {"url": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"noGo": {}, "type": "certscore_scan", "error": "texte", "jobId": "texte", "links": {}, "score": "texte", "domain": "texte", "scanId": "texte", "status": "texte", "coverage": "texte", "scanFrom": "eu_de", "createdAt": "texte"}}
Badge pour votre README
Ce serveur a passé le pentest comportemental. Le badge porte son nom et renvoie à cette fiche — la preuve, c'est la fiche (verdict live qu'on contrôle), pas l'image.
[](https://dokore.fr/serveur/ai.certscore--mcp-light)
<a href="https://dokore.fr/serveur/ai.certscore--mcp-light"><img src="https://dokore.fr/badge/ai.certscore--mcp-light.svg" alt="Vérifié par MCP Hub" height="20"></a>
Réévalué en continu : si le comportement change, le verdict tombe et le badge disparaît. Un badge qui ne pointe pas vers une fiche dokore.fr ne prouve rien. Comment ça marche
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é ».