_ registry / mcp + a2a streamable-http · checked 54m ago

frontend-checklist-mcp

https://mcp.frontendchecklist.io

Registry code: 949c2f2e53dcfc44

api record

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…

endpoint
https://mcp.frontendchecklist.io
door code
234574914e98b3c8
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is frontend-checklist-mcp live?
Yes — it answered the hub's last check (checked 54m ago). It answered 99% of checks over the last 30 days.
Is frontend-checklist-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does frontend-checklist-mcp have?
11 tools: get_workflow, get_checklist_rules, get_quick_reference, check_rule, get_rule, review_code, audit_url, fix_rule, ….
Is frontend-checklist-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.8%

90 days 99.3%· all time 99.2%

latency
341ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 1008 checks · signed record
  • down → live
  • degraded → live
  • degraded → down· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
_ what it is for
topic
developer tools testing & qa
used for
  • review frontend code against best practices
  • audit a web page html
  • get remediation steps for a frontend rule
  • get frontend checklists by category
takes → gives
code, web pages, text → data, text
tools
11 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 11 tools
2 open 9 never probed 2 of 11 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_categories reads open 7h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • search_rules reads open 7h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 100,
      "minimum": 1,
      "description": "Max results to return (default: 20, max: 100)"
    },
    "query": {
      "type": "string",
      "description": "Keywords to match, e.g. 'lazy loading images'. Omit to list rules by filters only."
    },
    "cursor": {
      "type": "string",
      "description": "Cursor from a previous response, to fetch the next page of results."
    },
    "categories": {
      "type": "array",
      "items": {
        "enum": [
          "html",
          "css",
          "javascript",
          "performance",
          "accessibility",
          "seo",
          "security",
          "images",
          "testing",
          "privacy",
          "pwa",
          "i18n"
        ],
        "type": "string"
      },
      "description": "Only return rules in these categories."
    },
    "priorities": {
      "type": "array",
      "items": {
        "enum": [
          "critical",
          "high",
          "medium",
          "low"
        ],
        "type": "string"
      },
      "description": "Only return rules with these priorities."
    }
  }
}
    arguments 55 lines
  • get_workflow reads unknown 54m ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "enum": [
        "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"
      ],
      "type": "string",
      "description": "The checklist workflow slug. Available: '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'"
    }
  }
}
    arguments 26 lines
  • get_checklist_rules reads unknown 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "checklist"
  ],
  "properties": {
    "checklist": {
      "enum": [
        "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"
      ],
      "type": "string",
      "description": "Checklist slug. Available: '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'"
    },
    "includeContent": {
      "type": "boolean",
      "description": "Include full MDX body content (large). Default false returns title, description, prompts, and metadata only."
    }
  }
}
    arguments 30 lines
  • get_quick_reference reads unknown 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "category"
  ],
  "properties": {
    "format": {
      "enum": [
        "json",
        "markdown",
        "checklist"
      ],
      "type": "string",
      "description": "Output format (default: 'json'). Use 'markdown' for readable docs, 'checklist' for copy-paste task lists."
    },
    "category": {
      "type": "string",
      "description": "Category name, e.g. 'accessibility', 'performance', or 'seo' (see list_categories)."
    },
    "priorityFilter": {
      "enum": [
        "all",
        "critical",
        "critical+high",
        "critical+high+medium"
      ],
      "type": "string",
      "description": "Filter by priority level (default: 'critical+high'). Use 'all' for comprehensive lists, 'critical' for essentials only."
    }
  }
}
    arguments 31 lines
  • check_rule reads unknown 25h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "Code to test against the rule. Omit to get manual verification steps."
    },
    "slug": {
      "type": "string",
      "description": "Rule slug: the kebab-case rule ID, e.g. 'alt-text' or 'doctype'. The ID must identify a rule in the published catalogue."
    }
  }
}
    arguments 16 lines
  • get_rule reads unknown 54m ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Rule slug: the kebab-case rule ID, e.g. 'alt-text' or 'doctype'. The ID must identify a rule in the published catalogue."
    },
    "includeUrl": {
      "type": "boolean",
      "description": "Include the rule's web URL in response (default: false)"
    }
  }
}
    arguments 16 lines
  • review_code reads unknown 54m ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "The HTML, CSS, or JavaScript source to review (a snippet or a whole file)."
    },
    "focus": {
      "type": "array",
      "items": {
        "enum": [
          "html",
          "css",
          "javascript",
          "performance",
          "accessibility",
          "seo",
          "security",
          "images"
        ],
        "type": "string"
      },
      "description": "Only check these categories (default: auto-detected from the code)."
    },
    "minPriority": {
      "enum": [
        "critical",
        "high",
        "medium",
        "low"
      ],
      "type": "string",
      "description": "Lowest priority to report (default: medium)."
    }
  }
}
    arguments 39 lines
  • audit_url reads unknown 25h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Public URL to audit. Must use https://. Private IPs and localhost are blocked."
    },
    "focus": {
      "type": "array",
      "items": {
        "enum": [
          "html",
          "css",
          "javascript",
          "performance",
          "accessibility",
          "seo",
          "security",
          "images"
        ],
        "type": "string"
      },
      "description": "Only check these categories (default: auto-detected from the fetched HTML)."
    },
    "minPriority": {
      "enum": [
        "critical",
        "high",
        "medium",
        "low"
      ],
      "type": "string",
      "description": "Lowest priority to report (default: medium)."
    }
  }
}
    arguments 39 lines
  • fix_rule reads unknown 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Rule slug: the kebab-case rule ID, e.g. 'alt-text' or 'doctype'. The ID must identify a rule in the published catalogue."
    },
    "codeSnippet": {
      "type": "string",
      "description": "Code that violates the rule, so the fix guidance can reference it."
    }
  }
}
    arguments 16 lines
  • explain_rule reads unknown 7h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Rule slug: the kebab-case rule ID, e.g. 'alt-text' or 'doctype'. The ID must identify a rule in the published catalogue."
    }
  }
}
    arguments 12 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 949c2f2e53dcfc44.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/949c2f2e53dcfc44/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/949c2f2e53dcfc44/badge.svg)](https://brick.blue/agent/949c2f2e53dcfc44?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.