Back to MCP servers

Front-End Checklist

https://mcp.frontendchecklist.io
● healthy

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

Transport
streamable-http
Auth
—
Cost
—
Protocol revision
2025-11-25
negotiated, not declared

MCP readiness

B · 83/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B+, 91.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 25/25 Endpoint answers the MCP initialize handshake (635 ms).
Protocol revision 8/10 Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 30/30 probes succeeded over 30 days (100%).
Tool declaration 10/10 Lists 11 tool(s) with descriptions.
Verified identity 7/10 Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags 0/5 not seen in a source for over 30 days.
Auth declaration 0/5 How to authenticate is not stated.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive (635 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-10.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 52,570 reachable MCP servers in our daily snapshot (2026-11-11 14:47 UTC). Display only; it does not change search order.

Readiness
Higher than 60% of peers
This listing 83 · peer median 81
Latency
Faster than 68% of peers
This listing 221 ms · peer median 371 ms

Where it loses the most points

  • Freshness + modern flags −5 — not seen in a source for over 30 days.
  • Auth declaration −5 — How to authenticate is not stated.
  • Verified identity −3 — Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).

How many agent tools actually work · All statistics

Adoption signals

Public signals from outside this directory, shown for context. They do not change search order or grades.

GitHub
★ 74,706 · 6,783 forks
last push 2026-10-31

Listed in

Directories this entry was found in.

mcp-registry since 2026-10-01 wellknown since 2026-10-03 ↗

How to connect

MCP endpoint (streamable-http)
https://mcp.frontendchecklist.io
JSON-RPC initialize probe
curl -X POST https://mcp.frontendchecklist.io \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://frontendchecklist.io/mcp
Source code
https://github.com/thedaviddias/Front-End-Checklist