Front-End Checklist

by thedaviddias · remote · no sign-in to list tools · v2.0.1 · published by GitHub user thedaviddias

Review frontend code and live pages against 386 quality-gated web development rules.

Changes · 2

Compare Registry entry

11 tools: 2 change things and 9 only read.

Scanned Oct 21, 2026

Deletes or cancels0Claude Code: deny
Can't be undone0Claude Code: ask
Changes things2Claude Code: ask: see these tools
Only reads9Claude Code: allow: see these tools

2 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http front-end-checklist https://mcp.frontendchecklist.io

Findings

Matches of fixed checks, with the text they matched.

2 warn

Warnreview_code
The server marks "review_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.
What this check looks for
Warncheck_rule
The server marks "check_rule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

11 tools

Changes things 2Creates or changes something that can be changed back.Claude Code: ask

check_ruleChecks a code snippet against one named frontend rule using static heuristics and returns findings and verification guidance.1 finding
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
  The server marks "check_rule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
  What this check looks for
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Check Rule Compliance
review_codeRuns a non-exhaustive static heuristic review of pasted HTML, CSS, or JavaScript against multiple frontend best practices and returns prioritized issues, fix guidance, and suggesti…1 finding
Why it is in this group
- The description's first verb is "run": a word for a change.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
  The server marks "review_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.
  What this check looks for
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Review Frontend Code

Only reads 9Looks things up and changes nothing.Claude Code: allow

audit_urlFetches a public HTTPS page and performs a non-exhaustive static review of its HTML, returning prioritized issues and fix guidance.No findings
Why it is in this group
- The description's first verb is "fetch": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- title: Audit Live URL
explain_ruleExplains one frontend rule, including its background, impact on users and the business, and related categories.No findings
Why it is in this group
- The name "explain_rule" says "explain": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Explain Frontend Rule
fix_ruleReturns step-by-step remediation guidance and priority for one named frontend rule.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Get Rule Fix
get_checklist_rulesReturns titles, priorities, verification and remediation prompts for every rule in a curated checklist.No findings
Why it is in this group
- The name "get_checklist_rules" says "get": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Get Checklist Rules
get_quick_referenceReturns a compact checklist for one frontend category, filtered by priority and formatted as JSON, Markdown, or a task list.No findings
Why it is in this group
- The name "get_quick_reference" says "get": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Get Quick Reference
get_ruleReturns complete guidance for one known rule slug: requirements, rationale, verification and remediation prompts, code examples, sources, and related rules.No findings
Why it is in this group
- The name "get_rule" says "get": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Get Rule Guidance
get_workflowReturns the ordered steps of a curated audit workflow, including rule slugs, priorities, and categories.No findings
Why it is in this group
- The name "get_workflow" says "get": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Get Audit Workflow
list_categoriesLists available frontend rule categories, their descriptions, and rule counts.No findings
Why it is in this group
- The name "list_categories" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: List Rule Categories
search_rulesFinds frontend rules by keywords, category, and priority, returning paginated slugs, titles, and short summaries.No findings
Why it is in this group
- The name "search_rules" says "search": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Search Frontend Rules

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 2.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http front-end-checklist https://mcp.frontendchecklist.io

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__front-end-checklist__audit_url",
      "mcp__front-end-checklist__get_workflow",
      "mcp__front-end-checklist__get_checklist_rules",
      "mcp__front-end-checklist__get_quick_reference",
      "mcp__front-end-checklist__get_rule",
      "mcp__front-end-checklist__search_rules",
      "mcp__front-end-checklist__fix_rule",
      "mcp__front-end-checklist__explain_rule",
      "mcp__front-end-checklist__list_categories"
    ],
    "ask": [
      "mcp__front-end-checklist__review_code",
      "mcp__front-end-checklist__check_rule"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as front-end-checklist. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.github.thedaviddias/front-end-checklist/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:50 UTC.

For agents: Markdown · JSON · report this listing