Connect Front-End Checklist and your agent gets 11 tools, among them audit_url, check_rule, explain_rule. It answers at https://mcp.frontendchecklist.io over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 1 October 2026; the last check, on 16 November 2026, succeeded.
Review frontend code and live pages against 386 quality-gated web development rules.
Description as the publisher wrote it.
| Tool | What 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 HTT Inputs: url, focus, minPriority |
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 Inputs: slug, code |
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 ap Inputs: slug |
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 a Inputs: slug, codeSnippet |
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 che Inputs: checklist, includeContent |
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. Inputs: category, priorityFilter, format |
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. Unkno Inputs: slug, includeUrl |
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, compreh Inputs: slug |
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 Inputs: code, focus, minPriority |
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. Inputs: query, categories, priorities, limit, cursor |
Every block below points at https://mcp.frontendchecklist.io. Pick your client and copy.
claude mcp add --transport http front-end-checklist https://mcp.frontendchecklist.io
{
"mcpServers": {
"front-end-checklist": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.frontendchecklist.io"]
}
}
}{
"mcpServers": {
"front-end-checklist": {
"url": "https://mcp.frontendchecklist.io"
}
}
}{
"servers": {
"front-end-checklist": {
"type": "http",
"url": "https://mcp.frontendchecklist.io"
}
}
}{
"context_servers": {
"front-end-checklist": {
"url": "https://mcp.frontendchecklist.io"
}
}
}{
"mcpServers": {
"front-end-checklist": {
"serverUrl": "https://mcp.frontendchecklist.io"
}
}
}{
"mcpServers": {
"front-end-checklist": {
"url": "https://mcp.frontendchecklist.io"
}
}
}name: Front-End Checklist
version: 0.0.1
schema: v1
mcpServers:
- name: Front-End Checklist
type: streamable-http
url: https://mcp.frontendchecklist.io{
"mcpServers": {
"front-end-checklist": {
"httpUrl": "https://mcp.frontendchecklist.io"
}
}
}{
"mcpServers": {
"front-end-checklist": {
"type": "http",
"url": "https://mcp.frontendchecklist.io"
}
}
}{
"mcpServers": {
"front-end-checklist": {
"url": "https://mcp.frontendchecklist.io"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.frontendchecklist.io&type=streamable_http&id=front-end-checklist&name=Front-End%20Checklist
It answered our last check on 16 November 2026 in 100 ms. Over 4 checks since 1 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
11, as returned by the server's own tools/list on 19 November 2026: audit_url, check_rule, explain_rule, fix_rule, get_checklist_rules, get_quick_reference, get_rule, get_workflow, and 3 more.
It answered our last check on 16 November 2026 in 100 ms. Over 4 checks since 1 October 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.frontendchecklist.io. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.thedaviddias. Endpoint host: mcp.frontendchecklist.io. ARD identifier: urn:air:io.github.thedaviddias:mcp:front-end-checklist.
First indexed 1 October 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.