Front-End Checklist

Name: Front-End Checklist
Author: thedaviddias

MCP serverMCP

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

by thedaviddiasrepository ↗homepage ↗v2.0.1

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"front-end-checklist","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability28/28 checks ok

when	check	result	http	latency	detail
1 h ago	mcp initialize	ok	200	141 ms	server frontend-checklist-mcp 2.0.1 · protocol 2025-06-18 · 11 tools
8 h ago	mcp initialize	ok	200	160 ms	server frontend-checklist-mcp 2.0.1 · protocol 2025-06-18 · 11 tools
14 h ago	mcp initialize	ok	200	141 ms	server frontend-checklist-mcp 2.0.1 · protocol 2025-06-18 · 11 tools
21 h ago	mcp initialize	ok	200	139 ms	server frontend-checklist-mcp 2.0.1 · protocol 2025-06-18 · 11 tools
27 h ago	mcp initialize	ok	200	146 ms	server frontend-checklist-mcp 2.0.1 · protocol 2025-06-18 · 11 tools
33 h ago	mcp initialize	ok	200	203 ms	server frontend-checklist-mcp 2.0.1 · protocol 2025-06-18 · 11 tools
2 d ago	mcp initialize	ok	200	233 ms	server frontend-checklist-mcp 2.0.1 · protocol 2025-06-18 · 11 tools
2 d ago	mcp initialize	ok	200	146 ms	server frontend-checklist-mcp 2.0.1 · protocol 2025-06-18 · 11 tools
2 d ago	mcp initialize	ok	200	217 ms	server frontend-checklist-mcp 2.0.1 · protocol 2025-06-18 · 11 tools
2 d ago	mcp initialize	ok	200	209 ms	server frontend-checklist-mcp 2.0.1 · protocol 2025-06-18 · 11 tools

Tools observed via MCP handshake

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 gu
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 request
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 a
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 che
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 con
get_rule — Returns complete guidance for one known rule slug: requirements, rationale, verification and remediation prompts, code examples, sources, and related rules. Use
search_rules — Finds frontend rules by keywords, category, and priority, returning paginated slugs, titles, and short summaries. Use it when the user requests relevant practic
check_rule — Checks a code snippet against one named frontend rule using static heuristics and returns findings and verification guidance. Without code, returns manual verif
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
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
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

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.thedaviddias/front-end-checklist

first seen 7 d ago · fetched 2 d agoopen ↗

Field history (9 recent events)

5 d ago · declared · homepageUrl → "https://frontendchecklist.io/mcp"
5 d ago · declared · version → "2.0.1"
7 d ago · declared · publisherName → "thedaviddias"
7 d ago · declared · homepageUrl → "https://frontendchecklist.io/en/mcp"
7 d ago · declared · summary → "Review frontend code and live pages against 386 quality-gated web development rules."
7 d ago · declared · version → "2.0.0"
7 d ago · declared · protocols → ["mcp"]
7 d ago · declared · repoUrl → "https://github.com/thedaviddias/Front-End-Checklist"
7 d ago · declared · description → "Review frontend code and live pages against 386 quality-gated web development rules."

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from