Front-End Checklist
REMOTE · MCP.FRONTENDCHECKLIST.IO
Review frontend code and live pages against 386 quality-gated web development rules.
Available components
Last scanned (21 hours ago)
Scores higher than 97% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability90
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 17666 tokens (~43/item across 410 items; 11 tools + 399 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.frontendchecklist.io
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.frontendchecklist.io | CN=YR1,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | RSA 2048 | SHA256-RSA | 66f8425542a571b10d0b552cfa4269e1c2f |
| SANs: mcp.frontendchecklist.io | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.frontendchecklist.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| frontendchecklist.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; img-src 'self' data: blob: https:; font-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; connect-src 'self'; frame-src 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.frontendchecklist.io | Verified | 200 | |
| http (plaintext) | http://mcp.frontendchecklist.io | HTTPS enforced | 308 | https://mcp.frontendchecklist.io/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_url Audit Live URL ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| focus | array | – | Only check these categories (default: auto-detected from the fetched HTML). |
| minPriority | string | – | Lowest priority to report (default: medium). |
| url | string | yes | Public URL to audit. Must use https://. Private IPs and localhost are blocked. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | – |
| issues | array | – | – |
| source | object | – | – |
| suggestions | array | – | – |
| summary | object | – | – |
No examples provided.
check_rule Check Rule Compliance ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Code to test against the rule. Omit to get manual verification steps. |
| slug | string | yes | Rule slug: the kebab-case rule ID, e.g. 'alt-text' or 'doctype'. The ID must identify a rule in the published catalogue. |
| Name | Type | Req | Description |
|---|---|---|---|
| analysis | string | – | – |
| categories | array | – | – |
| checkPrompt | string | – | – |
| fixPrompt | string | – | – |
| message | string | – | – |
| slug | string | – | – |
| suggestions | array | – | – |
| title | string | – | – |
No examples provided.
explain_rule Explain Frontend Rule ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Rule slug: the kebab-case rule ID, e.g. 'alt-text' or 'doctype'. The ID must identify a rule in the published catalogue. |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | – |
| explainPrompt | string | – | – |
| message | string | – | – |
| slug | string | – | – |
| suggestions | array | – | – |
| title | string | – | – |
No examples provided.
fix_rule Get Rule Fix ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| codeSnippet | string | – | Code that violates the rule, so the fix guidance can reference it. |
| slug | string | yes | Rule slug: the kebab-case rule ID, e.g. 'alt-text' or 'doctype'. The ID must identify a rule in the published catalogue. |
| Name | Type | Req | Description |
|---|---|---|---|
| codeContext | string | – | – |
| fixPrompt | string | – | – |
| message | string | – | – |
| priority | string | – | – |
| slug | string | – | – |
| suggestions | array | – | – |
| title | string | – | – |
No examples provided.
get_checklist_rules Get Checklist Rules ~214
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.
| Name | Type | Req | Description |
|---|---|---|---|
| checklist | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| checklist | object | – | – |
| error | object | – | – |
| rules | array | – | – |
No examples provided.
get_quick_reference Get Quick Reference ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Category name, e.g. 'accessibility', 'performance', or 'seo' (see list_categories). |
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| displayName | string | – | – |
| error | object | – | – |
| items | array | – | – |
| markdown | string | – | – |
| priorityFilter | string | – | – |
| totalCount | number | – | – |
No examples provided.
get_rule Get Rule Guidance ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| includeUrl | boolean | – | Include the rule's web URL in response (default: false) |
| slug | string | yes | Rule slug: the kebab-case rule ID, e.g. 'alt-text' or 'doctype'. The ID must identify a rule in the published catalogue. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No examples provided.
get_workflow Get Audit Workflow ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The checklist workflow slug. Available: 'accessibility-essentials', 'comprehensive-audit', 'core-web-vitals', 'html-foundations', 'image-optimization', 'javascript-resilience', 'launch-checklist', 'p… |
| Name | Type | Req | Description |
|---|---|---|---|
| criticalCount | number | – | – |
| description | string | – | – |
| difficulty | string | – | – |
| error | object | – | – |
| estimatedTime | string | – | – |
| highCount | number | – | – |
| icon | string | – | – |
| slug | string | – | – |
| steps | array | – | – |
| title | string | – | – |
| totalRules | number | – | – |
No examples provided.
list_categories List Rule Categories ~37
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | – |
No examples provided.
review_code Review Frontend Code ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The HTML, CSS, or JavaScript source to review (a snippet or a whole file). |
| focus | array | – | Only check these categories (default: auto-detected from the code). |
| minPriority | string | – | Lowest priority to report (default: medium). |
| Name | Type | Req | Description |
|---|---|---|---|
| issues | array | – | – |
| suggestions | array | – | – |
| summary | object | – | – |
No examples provided.
search_rules Search Frontend Rules ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Only return rules in these categories. |
| cursor | string | – | Cursor from a previous response, to fetch the next page of results. |
| limit | integer | – | Max results to return (default: 20, max: 100) |
| priorities | array | – | Only return rules with these priorities. |
| query | string | – | Keywords to match, e.g. 'lazy loading images'. Omit to list rules by filters only. |
| Name | Type | Req | Description |
|---|---|---|---|
| nextCursor | string | – | – |
| rules | array | – | – |
| totalCount | number | – | – |
No examples provided.
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.
remote · mcp.frontendchecklist.io
claude mcp add --transport http thedaviddias-front-end-checklist 'https://mcp.frontendchecklist.io/'
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 90 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,459 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Front-End Checklist MCP server?
VerifyMCP ran 14 checks on Front-End Checklist, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.