bots.st/front-end-checklist
Front-End Checklist
Audit frontend code and live pages against quality rules
1695 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 11
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://mcp.frontendchecklist.io
What it can do
| Tool | What it says it does |
|---|---|
audit_url | 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… |
check_rule | 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… |
explain_rule | 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. |
fix_rule | 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. |
get_checklist_rules | 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… |
get_quick_reference | 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. |
get_rule | 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. |
get_workflow | 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… |
list_categories | 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. |
review_code | 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… |
search_rules | 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. |
In its maker's words
Review frontend code and live pages against 386 quality-gated web development rules.
- Website
- frontendchecklist.io/mcp
- Source
- github.com/thedaviddias/Front-End-Checklist
- Publisher
- thedaviddias
- Listed from
- the official MCP Registry as
io.github.thedaviddias/front-end-checklist - Version
- 2.0.1, updated 4 Oct 2026
- Kinds of work
- Code and developer tools, Search and research
The domain it lives on
- frontendchecklist.io
- registered 20 Nov 2017 (8 years ago), at NameCheap, Inc., its home page is a working site
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 1695 ms | |
| Answered | 1546 ms | |
| Answered | 885 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.