mcpbeat Sign in

Front-End Checklist MCP Server

by thedaviddias Your server? Claim it
not responding

Front-End Checklist is listed as active in the registry but did not answer our last check. It exposes 11 tools. Last commit 6 Oct 2026.

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

Uptime history 39 days of history · worst day 0%
39 days agonow
0.0%
Uptime 24h
0 of 92 checks
11
Tools
read from the server
102 ms
Response time
average over 24h
74 679
Stars
last commit 6 Oct 2026

What changed 19

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 October 2026. No other catalogue keeps this.

8 Oct 11 tool descriptions were rewritten audit_url, check_rule, explain_rule and 8 more
8 Oct 8 tools changed the parameters they ask for audit_url, check_rule, explain_rule and 5 more

What the code does

We read the source, 1 d ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Builds a file path from a variable apps/web/lib/rule-content.ts:18 
  const fullPath = path.join(RULES_DIR, filePath)
Page executes code built at runtime packages/content/rules/en/javascript/avoid-eval.mdx:2, packages/content/rules/en/performance/streaming-html.mdx:274 
title: Never use eval() or unsafe dynamic code execution
Page loads a third-party script packages/content/rules/en/performance/fetchpriority-attribute.mdx:205, packages/content/rules/en/performance/http-requests.mdx:205, packages/content/rules/en/performance/third-party-scripts.mdx:100 и ещё 3 
<script
  src="https://cdn.example.com/analytics.js"

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add front-end-checklist --transport http https://mcp.frontendchecklist.io
Settings → Connectors → Add custom connector, then paste this address
https://mcp.frontendchecklist.io
~/.codex/config.toml
[mcp_servers.front-end-checklist]
url = "https://mcp.frontendchecklist.io"
.cursor/mcp.json
{
  "mcpServers": {
    "front-end-checklist": {
      "url": "https://mcp.frontendchecklist.io"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "front-end-checklist": {
      "type": "http",
      "url": "https://mcp.frontendchecklist.io"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

rule
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 runtime conformance.
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.
audit
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 live Core Web Vitals, or certify accessibility.
categories
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.
checklist
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, core-web-vitals, html-foundations, image-optimization, javascript-resilience, launch-checklist, performance-quick-wins, privacy-and-consent, security-audit, seo-audit, testing-checklist.
explain
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
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.
quick
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.
review
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 issue list means no provable static issue was found; it does not establish accessibility conformance or runtime correctness.
rules
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.
workflow
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, image-optimization, javascript-resilience, launch-checklist, performance-quick-wins, privacy-and-consent, security-audit, seo-audit, testing-checklist.

Endpoints

URLTransportStateLatencyChecked
https://mcp.frontendchecklist.io streamable-http answering 102 ms 0 min ago

Alternatives to Front-End Checklist

same job, measured the same way
Iris Code
by daiveedjay

Local code-quality rules, findings, preview-first safe fixes and gate results for coding agents.

142 installs/wk local only
Rams
by rams

Design review for UI code and live pages: quick checks, 0-100 scored reviews, fixes as patches

5 tools answering
T
Tribunal
by thebotclub

Tribunal — Enterprise Claude Code plugin. TDD enforcement, quality gates, vault of rules and agents.

63 installs/wk local only
Whoogy
by whoogy

Compare Figma designs against live websites and get visual + content QA reports, from inside Claude.

answering
Norma by Quality Clouds
by qualityclouds

Checks AI-written code against your rules as it is written, and keeps a record of what it found.

answering
Prumo
by tomd4vs

Checks the context files a coding agent reads against the git index, and reports what drifted.

77 installs/wk local only
VibeFix
by vibe-fixer

Free check by an AI agent on your live app. On request: independent code review, fix, live re-check.

7 tools answering
Agentsfile
by cloudcorprecords

Validate AGENTS.md and CLAUDE.md against repo reality: paths, scripts, and commands checked.

50 installs/wk local only

Front-End Checklist — questions

Answers built from our own checks of this server.

What can Front-End Checklist do?
It exposes 11 tools, read directly from the server on our last check. Among them: audit_url, check_rule, explain_rule, fix_rule, get_checklist_rules, get_quick_reference and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Front-End Checklist working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 102 ms. The bar chart above shows every period we have measured.
The registry lists Front-End Checklist as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Front-End Checklist?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Front-End Checklist need an API key?
No. Front-End Checklist completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
Is Front-End Checklist open source?
The code is open source: it is published under the MIT licence, written in MDX, 74 679 stars on GitHub and 5 open issues. The licence covers the code in the repository, not the hosted service at mcp.frontendchecklist.io, which runs on its operator's own terms.