io.github.thedaviddias/front-end-checklist

Est-ce que io.github.thedaviddias/front-end-checklist est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.thedaviddias/front-end-checklist » 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 11 outils

• audit_url≈ 488 tokens

  Fetches a public HTTPS page and performs a non-exhaustive static review of its HTML, returning prioritized issues and fix guidance. Use it when the user requests an audit of a deployed public page. Localhost, private networks, and plain HTTP URLs are refused. It does not execute the page, measure live Core Web Vitals, or certify accessibility.

  Paramètres, retour & exemple (3)

  Paramètres

  • url · string · requis
    Public URL to audit. Must use https://. Private IPs and localhost are blocked.
  • focus · array · optionnel
    Only check these categories (default: auto-detected from the fetched HTML).
  • minPriority · string · optionnel · critical | high | medium | low
    Lowest priority to report (default: medium).

  Exemple d'appel

  {"name": "audit_url", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": "texte", "issues": [], "source": {}, "summary": {}, "suggestions": []}}

• check_rule≈ 376 tokens

  Checks a code snippet against one named frontend rule using static heuristics and returns findings and verification guidance. Without code, returns manual verification guidance. Use it when the user requests a check of a specific rule or a proposed fix. Results do not establish rendered-state or runtime conformance.

  Paramètres, retour & exemple (2)

  Paramètres

  • code · string · optionnel
    Code to test against the rule. Omit to get manual verification steps.
  • slug · string · requis
    Rule slug: the kebab-case rule ID, e.g. 'alt-text' or 'doctype'. The ID must identify a rule in the published catalogue.

  Exemple d'appel

  {"name": "check_rule", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"slug": "texte", "title": "texte", "message": "texte", "analysis": "texte", "fixPrompt": "texte", "categories": [], "checkPrompt": "texte", "suggestions": []}}

• explain_rule≈ 316 tokens

  Explains one frontend rule, including its background, impact on users and the business, and related categories. Use it when the user asks why a practice matters or requests educational context. It returns explanation guidance rather than applying a fix.

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    Rule slug: the kebab-case rule ID, e.g. 'alt-text' or 'doctype'. The ID must identify a rule in the published catalogue.

  Exemple d'appel

  {"name": "explain_rule", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"slug": "texte", "title": "texte", "message": "texte", "categories": [], "suggestions": [], "explainPrompt": "texte"}}

• fix_rule≈ 318 tokens

  Returns step-by-step remediation guidance and priority for one named frontend rule. Use it when the user requests implementation or fix instructions for a known issue. Optional codeSnippet provides context; the tool does not edit files or apply changes.

  Paramètres, retour & exemple (2)

  Paramètres

  • slug · string · requis
    Rule slug: the kebab-case rule ID, e.g. 'alt-text' or 'doctype'. The ID must identify a rule in the published catalogue.
  • codeSnippet · string · optionnel
    Code that violates the rule, so the fix guidance can reference it.

  Exemple d'appel

  {"name": "fix_rule", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"slug": "texte", "title": "texte", "message": "texte", "priority": "critical", "fixPrompt": "texte", "codeContext": "texte", "suggestions": []}}

• get_checklist_rules≈ 607 tokens

  Returns titles, priorities, verification and remediation prompts for every rule in a curated checklist. Use it when the user requests guidance for an entire checklist. includeContent optionally adds each rule’s long-form body. Available checklists: accessibility-essentials, comprehensive-audit, core-web-vitals, html-foundations, image-optimization, javascript-resilience, launch-checklist, performance-quick-wins, privacy-and-consent, security-audit, seo-audit, testing-checklist.

  Paramètres, retour & exemple (2)

  Paramètres

  • checklist · string · requis · accessibility-essentials | comprehensive-audit | core-web-vitals | html-foundations | image-optimization | javascript-resilience | launch-checklist | performance-quick-wins
    Checklist slug. Available: 'accessibility-essentials', 'comprehensive-audit', 'core-web-vitals', 'html-foundations', 'image-optimization', 'javascript-resilience', 'launch-checklist', 'performance-quick-wins', 'privacy-and-consent', 'security-audit', 'seo-audit', 'testing-checklist'
  • includeContent · boolean · optionnel
    Include full MDX body content (large). Default false returns title, description, prompts, and metadata only.

  Exemple d'appel

  {"name": "get_checklist_rules", "arguments": {"checklist": "accessibility-essentials"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "rules": [], "checklist": {}}}

• get_quick_reference≈ 410 tokens

  Returns a compact checklist for one frontend category, filtered by priority and formatted as JSON, Markdown, or a task list. Use it when the user requests a concise checklist for a deployment, review, or team handoff.

  Paramètres, retour & exemple (3)

  Paramètres

  • format · string · optionnel · json | markdown | checklist
    Output format (default: 'json'). Use 'markdown' for readable docs, 'checklist' for copy-paste task lists.
  • category · string · requis
    Category name, e.g. 'accessibility', 'performance', or 'seo' (see list_categories).
  • priorityFilter · string · optionnel · all | critical | critical+high | critical+high+medium
    Filter by priority level (default: 'critical+high'). Use 'all' for comprehensive lists, 'critical' for essentials only.

  Exemple d'appel

  {"name": "get_quick_reference", "arguments": {"category": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "items": [], "category": "texte", "markdown": "texte", "totalCount": 1, "displayName": "texte", "priorityFilter": "texte"}}

• get_rule≈ 620 tokens

  Returns complete guidance for one known rule slug: requirements, rationale, verification and remediation prompts, code examples, sources, and related rules. Use it when the user requests detailed guidance for a specific frontend rule. Unknown slugs return similar suggestions.

  Paramètres, retour & exemple (2)

  Paramètres

  • slug · string · requis
    Rule slug: the kebab-case rule ID, e.g. 'alt-text' or 'doctype'. The ID must identify a rule in the published catalogue.
  • includeUrl · boolean · optionnel
    Include the rule's web URL in response (default: false)

  Exemple d'appel

  {"name": "get_rule", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "slug": "texte", "title": "texte", "content": "texte", "message": "texte", "prompts": {}, "sources": [], "priority": "critical", "aiContext": "texte", "categories": [], "difficulty": "texte", "description": "texte"}}

• get_workflow≈ 509 tokens

  Returns the ordered steps of a curated audit workflow, including rule slugs, priorities, and categories. Use it when the user requests a structured audit such as a pre-launch checklist. Available workflows: accessibility-essentials, comprehensive-audit, core-web-vitals, html-foundations, image-optimization, javascript-resilience, launch-checklist, performance-quick-wins, privacy-and-consent, security-audit, seo-audit, testing-checklist.

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis · accessibility-essentials | comprehensive-audit | core-web-vitals | html-foundations | image-optimization | javascript-resilience | launch-checklist | performance-quick-wins
    The checklist workflow slug. Available: 'accessibility-essentials', 'comprehensive-audit', 'core-web-vitals', 'html-foundations', 'image-optimization', 'javascript-resilience', 'launch-checklist', 'performance-quick-wins', 'privacy-and-consent', 'security-audit', 'seo-audit', 'testing-checklist'

  Exemple d'appel

  {"name": "get_workflow", "arguments": {"slug": "accessibility-essentials"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"icon": "texte", "slug": "texte", "error": {}, "steps": [], "title": "texte", "highCount": 1, "difficulty": "texte", "totalRules": 1, "description": "texte", "criticalCount": 1, "estimatedTime": "texte"}}

• list_categories≈ 186 tokens

  Lists available frontend rule categories, their descriptions, and rule counts. Use it when the user asks what the checklist covers or needs valid category names.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_categories", "arguments": {}}

  Exemple de retour

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

• review_code≈ 465 tokens

  Runs a non-exhaustive static heuristic review of pasted HTML, CSS, or JavaScript against multiple frontend best practices and returns prioritized issues, fix guidance, and suggestions for manual verification. Use it when the user requests a review, audit, or debugging of source code. An empty issue list means no provable static issue was found; it does not establish accessibility conformance or runtime correctness.

  Paramètres, retour & exemple (3)

  Paramètres

  • code · string · requis
    The HTML, CSS, or JavaScript source to review (a snippet or a whole file).
  • focus · array · optionnel
    Only check these categories (default: auto-detected from the code).
  • minPriority · string · optionnel · critical | high | medium | low
    Lowest priority to report (default: medium).

  Exemple d'appel

  {"name": "review_code", "arguments": {"code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"issues": [], "summary": {}, "suggestions": []}}

• search_rules≈ 477 tokens

  Finds frontend rules by keywords, category, and priority, returning paginated slugs, titles, and short summaries. Use it when the user requests relevant practices for a technology, concern, or pattern, such as web fonts or accessible forms.

  Paramètres, retour & exemple (5)

  Paramètres

  • limit · integer · optionnel
    Max results to return (default: 20, max: 100)
  • query · string · optionnel
    Keywords to match, e.g. 'lazy loading images'. Omit to list rules by filters only.
  • cursor · string · optionnel
    Cursor from a previous response, to fetch the next page of results.
  • categories · array · optionnel
    Only return rules in these categories.
  • priorities · array · optionnel
    Only return rules with these priorities.

  Exemple d'appel

  {"name": "search_rules", "arguments": {"limit": 1, "query": "texte", "cursor": "texte", "categories": [], "priorities": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"rules": [], "nextCursor": "texte", "totalCount": 1}}

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://mcp.frontendchecklist.io