Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Front-End Checklist is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
11
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Review frontend code and live pages against 386 quality-gated web development rules.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http front-end-checklist-mcp https://mcp.frontendchecklist.io
# 2 — ask your agent for something these tools do
# review_code, audit_url, get_workflow and 8 more
Front-End Checklist costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
THAll 1 server
thedaviddias1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http front-end-checklist-mcp https://mcp.frontendchecklist.ioReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
No parameter schema on file.
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 issu
No parameter schema on file.
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,
No parameter schema on file.
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, javascri
No parameter schema on file.
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.
No parameter schema on file.
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 issue
No parameter schema on file.
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 l
No parameter schema on file.
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 re
No parameter schema on file.
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 expl
No parameter schema on file.
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
No parameter schema on file.
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 rev
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Front-End Checklist or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.0.1.
2.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Front-End Checklist can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.