# Front-End Checklist (remote · mcp.frontendchecklist.io)

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

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-05

## Components

- remote · `mcp.frontendchecklist.io`: 78/100 (this document), [markdown](https://verifymcp.io/servers/thedaviddias-front-end-checklist/mcp.md), [page](https://verifymcp.io/servers/thedaviddias-front-end-checklist/mcp)

## Channel facts

- Endpoint: `https://mcp.frontendchecklist.io`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 89/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 18046 tokens (~44/item across 410 items; 11 tools + 399 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Front-End Checklist MCP server?

Front-End Checklist is a hosted endpoint at https://mcp.frontendchecklist.io/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http thedaviddias-front-end-checklist 'https://mcp.frontendchecklist.io/'
```

### Cursor

```json
{
  "mcpServers": {
    "thedaviddias-front-end-checklist": {
      "url": "https://mcp.frontendchecklist.io/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "thedaviddias-front-end-checklist": {
      "type": "http",
      "url": "https://mcp.frontendchecklist.io/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.thedaviddias-front-end-checklist]
url = "https://mcp.frontendchecklist.io/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "thedaviddias-front-end-checklist": {
      "type": "remote",
      "url": "https://mcp.frontendchecklist.io/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add thedaviddias-front-end-checklist --url 'https://mcp.frontendchecklist.io/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  thedaviddias-front-end-checklist:
    url: "https://mcp.frontendchecklist.io/"
```

### Netclaw

```json
{
  "McpServers": {
    "thedaviddias-front-end-checklist": {
      "Transport": "http",
      "Url": "https://mcp.frontendchecklist.io/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add thedaviddias-front-end-checklist -t streamable-http -u 'https://mcp.frontendchecklist.io/'
```

### Other

```json
{
  "mcpServers": {
    "thedaviddias-front-end-checklist": {
      "type": "http",
      "url": "https://mcp.frontendchecklist.io/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-05 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-03 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-02 (score 76, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-01 (score 76)

First indexed and scored.

## MCP tools (11)

### `review_code` (~223 tokens)

Review Frontend Code

\**PROACTIVE CODE REVIEW**: Runs a conservative, non-exhaustive static heuristic review of HTML/CSS/JS code against multiple frontend best practice rules simultaneously. **Use this tool FIRST** when reviewing, debugging, or improving any frontend code - it detects the code type and checks relevant rules it can prove from the snippet. Returns prioritized issues with fix guidance when static evidence is available, plus suggestions for rule retrieval when manual or rendered-state review is needed.

\**Workflow:** Use as the FIRST step for any code review. For each issue found, use fix_rule for remediation guidance or get_rule for complete context. If no issues are returned, treat that as "no provable static issue found", then follow suggestions with search_rules or get_rule before concluding the implementation is clean.

Input parameters:

- `code` (string, required): The HTML, CSS, or JavaScript code to review
- `focus` (array): Optional: Focus review on specific categories (default: auto-detect from code)
- `minPriority` (string): Optional: Minimum priority level to report (default: medium)

Output parameters:

- `issues` (array)
- `suggestions` (array)
- `summary` (object)

### `audit_url` (~154 tokens)

Audit Live URL

Fetches a public URL and audits its HTML against frontend best practice rules. **Use this tool** when you want to check a live website without manually pasting HTML. Automatically fetches the page source and runs the same heuristic checks as review_code.

\**Workflow:** Call audit_url with a public https:// URL → get back a prioritized issue list → use fix_rule for remediation guidance on each issue.

Input parameters:

- `focus` (array): Optional: Focus review on specific categories (default: auto-detect from fetched HTML)
- `minPriority` (string): Optional: Minimum priority level to report (default: medium)
- `url` (string, required): Public URL to audit. Must use https://. Private IPs and localhost are blocked.

Output parameters:

- `error` (string)
- `issues` (array)
- `source` (object)
- `suggestions` (array)
- `summary` (object)

### `get_workflow` (~209 tokens)

Get Audit Workflow

Returns a curated, ordered sequence of rules for a specific checklist workflow. **Use PROACTIVELY** when performing comprehensive audits or setting up new projects. 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.

\**Workflow:** Use this tool FIRST to get a structured approach, then use get_rule for each step's details, and check_rule to validate code against each rule.

Input parameters:

- `slug` (string, required): The checklist workflow slug. Available: 'accessibility-essentials', 'comprehensive-audit', 'core-web-vitals', 'html-foundations', 'image-optimization', 'javascript-resilience', 'launch-checklist', 'p…

Output parameters:

- `criticalCount` (number)
- `description` (string)
- `difficulty` (string)
- `error` (object)
- `estimatedTime` (string)
- `highCount` (number)
- `icon` (string)
- `slug` (string)
- `steps` (array)
- `title` (string)
- `totalRules` (number)

### `get_checklist_rules` (~226 tokens)

Get Checklist Rules

Returns full rule details for every rule in a curated checklist in a single call. **More efficient than calling get_rule N times** after get_workflow. Use when you need the complete rule content for an entire checklist to perform a comprehensive audit or code review. 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.

Input parameters:

- `checklist` (string, required): Checklist slug. Available: 'accessibility-essentials', 'comprehensive-audit', 'core-web-vitals', 'html-foundations', 'image-optimization', 'javascript-resilience', 'launch-checklist', 'performance-qu…
- `includeContent` (boolean): Include full MDX body content (large). Default false returns title, description, prompts, and metadata only.

Output parameters:

- `checklist` (object)
- `error` (object)
- `rules` (array)

### `get_quick_reference` (~182 tokens)

Get Quick Reference

Returns a compact, actionable checklist of rules for a category. **Use PROACTIVELY** for CI/CD integration, quick audits, or generating checklists. Supports filtering by priority and multiple output formats.

\**Workflow:** Use for generating quick checklists before deployment or for team handoffs. Pair with check_rule to validate specific items, or get_rule for detailed guidance on any item.

Input parameters:

- `category` (string, required): The category to get a quick reference for (e.g., 'accessibility', 'performance', 'seo')
- `format` (string): Output format (default: 'json'). Use 'markdown' for readable docs, 'checklist' for copy-paste task lists.
- `priorityFilter` (string): Filter by priority level (default: 'critical+high'). Use 'all' for comprehensive lists, 'critical' for essentials only.

Output parameters:

- `category` (string)
- `displayName` (string)
- `error` (object)
- `items` (array)
- `markdown` (string)
- `priorityFilter` (string)
- `totalCount` (number)

### `get_rule` (~182 tokens)

Get Rule Guidance

Retrieves a single frontend development rule by its unique slug. **Use PROACTIVELY** when reviewing or debugging frontend code to get best practice guidance. Returns complete rule details including content, prompts (check/fix/explain), and metadata as Markdown with code examples. If the slug doesn't exist, returns suggestions for similar rules.

\**Workflow:** Use after review_code identifies issues, or after search_rules finds relevant rules. Follow up with check_rule to validate code, fix_rule to get remediation steps, or explain_rule to understand why it matters.

\**Related Rules:** This tool includes related rules in its response, helping you discover connected best practices and build comprehensive understanding.

Input parameters:

- `includeUrl` (boolean): Include the rule's web URL in response (default: false)
- `slug` (string, required): The rule's unique slug (e.g., 'doctype', 'alt-text')

Output parameters:

- `aiContext` (string)
- `categories` (array)
- `content` (string)
- `description` (string)
- `difficulty` (string)
- `estimatedTime` (number)
- `message` (string)
- `primaryCategory` (string)
- `priority` (string)
- `prompts` (object)
- `relatedRules` (array)
- `slug` (string)
- `sourceSummary` (object)
- `sources` (array)
- `subcategory` (string)
- `suggestions` (array)
- `title` (string)
- `url` (string)

### `search_rules` (~183 tokens)

Search Frontend Rules

Searches and filters frontend development rules. **Use PROACTIVELY** when working on frontend code to find relevant best practices - search by technology (e.g., "react", "images"), concern (e.g., "accessibility", "performance"), or specific patterns. Returns summary information for each match - use get_rule for full details.

\**Workflow:** Use as a discovery tool before diving deeper. Start with list_categories to see available areas, then search_rules to find specific rules, then get_rule for complete details including code examples.

Input parameters:

- `categories` (array): Filter by categories (array)
- `cursor` (string): Pagination cursor from previous response
- `limit` (integer): Max results to return (default: 20, max: 100)
- `priorities` (array): Filter by priorities (array)
- `query` (string): Free-text search query

Output parameters:

- `nextCursor` (string)
- `rules` (array)
- `totalCount` (number)

### `check_rule` (~144 tokens)

Check Rule Compliance

Checks code against a specific frontend rule. **Use PROACTIVELY** when reviewing HTML/CSS/JS code to validate against frontend best practices. Without code, returns verification guidance. With code, performs heuristic analysis and reports compliance status. If issues are found, includes the fix prompt for immediate remediation.

\**Workflow:** Use after search_rules finds relevant rules, or when review_code flags a specific issue. Follow up with fix_rule for remediation steps or explain_rule to understand why the rule matters.

Input parameters:

- `code` (string): Code snippet to analyze against the rule (optional)
- `slug` (string, required): The rule's slug (e.g., 'doctype', 'alt-text')

Output parameters:

- `analysis` (string)
- `categories` (array)
- `checkPrompt` (string)
- `fixPrompt` (string)
- `message` (string)
- `slug` (string)
- `suggestions` (array)
- `title` (string)

### `fix_rule` (~125 tokens)

Get Rule Fix

Retrieves the fix/implementation prompt for a specific rule. **Use PROACTIVELY** after identifying issues in frontend code to get step-by-step remediation guidance. Returns detailed instructions on how to fix the issue correctly, with priority level to help triage multiple issues.

\**Workflow:** Use after review_code or check_rule identifies issues. Pair with get_rule for complete context, or explain_rule to help users understand the importance of the fix.

Input parameters:

- `codeSnippet` (string): Optional: code or HTML snippet for context-aware fix suggestion
- `slug` (string, required): The rule's slug

Output parameters:

- `codeContext` (string)
- `fixPrompt` (string)
- `message` (string)
- `priority` (string)
- `slug` (string)
- `suggestions` (array)
- `title` (string)

### `explain_rule` (~116 tokens)

Explain Frontend Rule

Retrieves the educational explanation for a frontend rule. **Use PROACTIVELY** when the user asks "why" about frontend practices, or when explaining code review feedback. Provides context on why the rule matters, its background, and impact on web development. Categories help connect related concepts.

\**Workflow:** Use when users question a recommendation, or after fix_rule to provide educational context. Pair with check_rule to validate understanding, or search_rules to find related best practices in the same category.

Input parameters:

- `slug` (string, required): The rule's slug

Output parameters:

- `categories` (array)
- `explainPrompt` (string)
- `message` (string)
- `slug` (string)
- `suggestions` (array)
- `title` (string)

### `list_categories` (~95 tokens)

List Rule Categories

Lists all available rule categories with their rule counts. **Use PROACTIVELY** at the start of a frontend project review to understand what best practice areas are available (accessibility, performance, SEO, security, etc.) and plan a comprehensive code review strategy.

\**Workflow:** Use FIRST when starting a comprehensive audit. Follow up with search_rules to explore specific categories, or review_code to automatically check code against rules in those categories.

Output parameters:

- `categories` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/thedaviddias-front-end-checklist/mcp#diagnostics

## Score history

- 2026-10-05: 78
- 2026-10-04: 77
- 2026-10-03: 77
- 2026-10-02: 76
- 2026-10-01: 76

## Common questions

### What is the Front-End Checklist MCP server?

Front-End Checklist is an MCP server listed in the public MCP registry as io.github.thedaviddias/front-end-checklist. Review frontend code and live pages against 386 quality-gated web development rules. This page covers its hosted endpoint (https://mcp.frontendchecklist.io).

### Is the Front-End Checklist MCP server safe to use?

Front-End Checklist scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Front-End Checklist MCP server expose?

Front-End Checklist exposes 11 tools: review_code, audit_url, get_workflow, get_checklist_rules, get_quick_reference, and 6 more. Their descriptions and schemas cost roughly 1,839 tokens of context every time the server is loaded.

### Does the Front-End Checklist MCP server require authentication?

No. We connected to Front-End Checklist without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Front-End Checklist MCP server still maintained?

Front-End Checklist is still listed as active in the MCP registry. We last reached this channel on 5 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.frontendchecklist.io/
- Repository: https://github.com/thedaviddias/Front-End-Checklist
- Website: https://frontendchecklist.io/mcp
- Changelog RSS feed: https://verifymcp.io/servers/thedaviddias-front-end-checklist/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/thedaviddias-front-end-checklist/mcp.json
- HTML version of this page: https://verifymcp.io/servers/thedaviddias-front-end-checklist/mcp