Front-End Checklist

Name: Front-End Checklist
Author: thedaviddias

Review frontend code and live pages against 386 quality-gated web development rules.

by thedaviddias(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from the official MCP registry - entry io.github.thedaviddias/front-end-checklist v2.0.0. Ratings and installs below are from this marketplace.

Front-End Checklist

Review frontend code and live pages against 386 quality-gated web development rules.

Remote endpoints

streamable-http https://mcp.frontendchecklist.io

Source: https://github.com/thedaviddias/Front-End-Checklist

Registry entry: io.github.thedaviddias/front-end-checklist

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

# after Install: the listing is in your workspace's routing pool - nothing else to configure
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
# or pin it on the OpenAI-compatible endpoint: {"model": "mcp-io-github-thedaviddias-front-end-checklist", ...}

Installed into a catalogue, chosen by a router

Install Front-End Checklist and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Photo: RDNE Stock project

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

mcp-io-github-thedaviddias-front-end-checklist.ocm.jsonjson

{
  "ocm": "1",
  "id": "mcp-io-github-thedaviddias-front-end-checklist",
  "kind": "tool",
  "name": "Front-End Checklist",
  "description": "Review frontend code and live pages against 386 quality-gated web development rules.",
  "publisher": "thedaviddias",
  "version": "2.0.0",
  "capabilities": {
    "domains": [
      "coding"
    ],
    "tags": [
      "mcp",
      "mcp-server",
      "mcp-registry"
    ],
    "languages": [
      "en"
    ],
    "supports_tools": true
  },
  "quality_prior": 0.6,
  "examples": [
    "Review frontend code and live pages against 386 quality-gated web development rules."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "mcp-registry",
      "repository": "https://github.com/thedaviddias/Front-End-Checklist",
      "path": "server.json",
      "ref": "2.0.0",
      "url": "https://github.com/thedaviddias/Front-End-Checklist",
      "key": "io.github.thedaviddias/front-end-checklist",
      "registry": "https://registry.modelcontextprotocol.io"
    }
  },
  "endpoints": [
    {
      "protocol": "mcp",
      "url": "https://mcp.frontendchecklist.io"
    }
  ]
}

Fetch it by URL: GET /api/v1/registry/mcp-io-github-thedaviddias-front-end-checklist/manifest?version=2.0.0

About

Front-End Checklist

Remote endpoints

Use it

Install Front-End Checklist and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews