Front-End Checklist

MCP server by thedaviddias

Review frontend code and live public pages against hundreds of web development rules covering accessibility, performance, SEO and security.

No sign-in (No account or key needed)Streamable HTTP

Connect to Front-End Checklist

No sign-in needed. Connect with Front-End Checklist’s own URL:

https://mcp.frontendchecklist.io

Paste it into any client that supports remote MCP servers. Your client talks to thedaviddias directly, not through mcp.tc.

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/front-end-checklist

About

Gives an assistant access to the Front-End Checklist rule set, about 386 rules across HTML, CSS, JavaScript, performance, accessibility, SEO, security, images, testing, privacy and i18n. It can run a static heuristic review of pasted code, audit a public URL, and fetch, check, explain or fix individual rules. Curated workflows such as launch-checklist and core-web-vitals are also available.

The server is hosted at a public streamable HTTP endpoint. No sign-in or API key is needed. A local stdio version is also in the project repository. The code review is a conservative static pass, so an empty result does not prove the code is clean.

What you can do

  • Review pasted HTML, CSS, JS, React or Next.js code against many rules at once
  • Audit a live public https page
  • Search rules by keyword, category or priority
  • Get a rule's full guidance, fix steps or explanation
  • Check code against a specific rule
  • Run curated workflows such as launch or security audits
  • Generate quick reference checklists by category

Tools 11

  • review_codeRead-only

    Static heuristic review of frontend code against multiple rules, returning prioritized issues.

  • audit_urlRead-only

    Fetch a public URL and audit its HTML against frontend rules.

  • get_workflowRead-only

    Get an ordered sequence of rules for a checklist workflow such as seo-audit.

  • get_checklist_rulesRead-only

    Get full rule details for every rule in a curated checklist in one call.

  • get_quick_referenceRead-only

    Get a compact checklist of rules for a category, filterable by priority.

  • get_ruleRead-only

    Retrieve one rule by slug with content, prompts and metadata.

  • search_rulesRead-only

    Search and filter rules by query, category or priority.

  • check_ruleRead-only

    Check code against a specific rule or get verification guidance.

  • fix_ruleRead-only

    Get the fix and implementation prompt for a rule.

  • explain_ruleRead-only

    Get the educational explanation of why a rule matters.

  • list_categoriesRead-only

    List rule categories with rule counts.

Read from the live server on 7 Oct 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.

Example prompts

  • Use Front-End Checklist to review this React component and list the highest-confidence issues.

  • Audit https://example.com for accessibility, performance and SEO problems.

  • Explain the canonical URL rule and show how to fix it.

  • Run the launch-checklist workflow for my site.

Set up

Every client connects to mcp.frontendchecklist.io. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http front-end-checklist https://mcp.frontendchecklist.io
  1. Start Claude Code and type /mcp. front-end-checklist should show as connected.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Customize → Connectors, click + Add, then Add custom connector.
  2. Name it Front-End Checklist and paste this URL:
https://mcp.frontendchecklist.io
  1. Click Add. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://mcp.frontendchecklist.io and click Add.
  2. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, open Settings → Security and login and turn on Developer mode.
  2. Go to chatgpt.com/plugins and click + to create an app for a remote MCP server.
  3. Paste https://mcp.frontendchecklist.io as the server URL and choose No authentication.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

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

VS Code

Or from a terminal:

code --add-mcp '{"name":"front-end-checklist","type":"http","url":"https://mcp.frontendchecklist.io"}'

Or commit it to the repo in .vscode/mcp.json:

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

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "front-end-checklist": {
      "serverUrl": "https://mcp.frontendchecklist.io"
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add front-end-checklist --url https://mcp.frontendchecklist.io

Or edit ~/.codex/config.toml directly:

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

Gemini CLI

gemini mcp add --transport http front-end-checklist https://mcp.frontendchecklist.io

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.

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

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://mcp.frontendchecklist.io.

Embed

Show Front-End Checklist in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![Front-End Checklist on mcp.tc](https://mcp.tc/i/front-end-checklist/badge.svg)](https://mcp.tc/i/front-end-checklist)
HTML
<a href="https://mcp.tc/i/front-end-checklist"><img src="https://mcp.tc/i/front-end-checklist/badge.svg" alt="Front-End Checklist on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/front-end-checklist.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/front-end-checklist" title="Front-End Checklist on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/front-end-checklist.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Front-End Checklist card to your site.

Markdown
Add the mcp.tc card for Front-End Checklist, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/front-end-checklist.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="front-end-checklist"><a href="https://mcp.tc/i/front-end-checklist">Front-End Checklist on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![Front-End Checklist on mcp.tc](https://mcp.tc/i/front-end-checklist/badge.svg)](https://mcp.tc/i/front-end-checklist)
```

Reference: https://mcp.tc/embed

Change history

We read this server’s tool list every 3 hours and record what changes. Last read 8 Oct 2026, 07:29 UTC.

Follow Front-End Checklist and we’ll email you when something changes.

  1. , Automatic check

    Tracking started: 11 tools.

FAQ

Can I paste mcp.tc/i/front-end-checklist into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://mcp.frontendchecklist.io, so your client talks to Front-End Checklist directly. The quick link is for sharing: it opens this page, with setup steps for every client.

Does Front-End Checklist need an API key or a sign-in?

No. Front-End Checklist doesn’t ask for an account or key.

Is Front-End Checklist a remote or a local server?

Remote. thedaviddias hosts it at https://mcp.frontendchecklist.io, and it speaks Streamable HTTP. There’s nothing to install.

What can Front-End Checklist do?

It has 11 tools, including review_code, audit_url and get_workflow. You can review pasted HTML, CSS, JS, React or Next.js code against many rules at once, audit a live public https page and search rules by keyword, category or priority.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Does mcp.tc track changes to Front-End Checklist?

Yes. Front-End Checklist’s History tab shows each change we find to its tools, down to descriptions and parameters, plus new versions and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read Front-End Checklist’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with thedaviddias. This page was built from Front-End Checklist’s public metadata, last checked on 7 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.