Developer Tools

frontendchecklist.io

Provides frontend code review, URL auditing, and curated checklists for HTML/CSS/JS best practices.

1 endpoint11 known toolsFirst detected October 1, 2026Last detected October 1, 2026

ENDPOINT 1

https://mcp.frontendchecklist.io

No auth detected

MCP server metadata

Name: frontend-checklist-mcp
Version: 2.0.0

Capabilities

toolspromptsresourcesextensions.io.modelcontextprotocol/uiextensions.io.modelcontextprotocol/skillscompletions

Server instructions

Use Front-End Checklist whenever the user is reviewing, implementing, debugging, or auditing frontend code. Reach for this server for HTML, CSS, JavaScript, TypeScript, React, Next.js, accessibility, performance, SEO, security, images, privacy, i18n, testing, and launch-readiness work. For pasted or inspected frontend code, call review_code first as a conservative static heuristic pass, then use its suggestions plus search_rules, get_rule, fix_rule, explain_rule, or check_rule for deeper remediation. If review_code returns no issues, treat that as no provable static issue found; follow suggestions or retrieve relevant rules before concluding the implementation is clean. For broad audits, call get_workflow or get_checklist_rules before checking individual rules. For live public pages, use audit_url.

Known tools 11

review_code

**PROACTIVE CODE REVIEW**: Runs a conservative, non-exhaustive static heuristic review of HTML/CSS/JS code against multiple frontend best practice rules simultaneously.

Inferred read-only

audit_url

Fetches a public URL and audits its HTML against frontend best practice rules.

Inferred read-only

get_workflow

Returns a curated, ordered sequence of rules for a specific checklist workflow.

Inferred read-only

get_checklist_rules

Returns full rule details for every rule in a curated checklist in a single call.

Inferred read-only

get_quick_reference

Returns a compact, actionable checklist of rules for a category.

Inferred read-only

get_rule

Retrieves a single frontend development rule by its unique slug.

Inferred read-only

search_rules

Searches and filters frontend development rules.

Inferred read-only

check_rule

Checks code against a specific frontend rule.

Inferred read-only

fix_rule

Retrieves the fix/implementation prompt for a specific rule.

Inferred read-only

explain_rule

Retrieves the educational explanation for a frontend rule.

Inferred read-only

list_categories

Lists all available rule categories with their rule counts.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.frontend-checklist-mcp]
url = "https://mcp.frontendchecklist.io"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "frontend-checklist-mcp": {
      "type": "http",
      "url": "https://mcp.frontendchecklist.io"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: frontend-checklist-mcp
Remote MCP URL: https://mcp.frontendchecklist.io

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "frontend-checklist-mcp": {
      "url": "https://mcp.frontendchecklist.io"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "frontend-checklist-mcp": {
      "type": "http",
      "url": "https://mcp.frontendchecklist.io"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "frontend-checklist-mcp",
  "transport": "streamable-http",
  "url": "https://mcp.frontendchecklist.io"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for frontendchecklist.io was fetched 2026-10-03T07:18:21.042Z.

Trust status Trusted

frontendchecklist.io is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.