A Next.js-based web application for browsing and recommending MCP (Model Context Protocol) servers with LLM-powered recommendations
This is a Next.js web application, not an MCP server. The two 'tools' are HTTP API routes (GET /api/mcp, POST /api/recommend), not MCP tool definitions. No MCP protocol implementation is visible. Tool names lack action verbs (should be 'search_mcp_items', 'get_mcp_recommendations'). Descriptions are present but generic. Input schemas are partially visible but lack type constraints, enums, and validation rules. No output schemas documented. No error handling guidance. The codebase shows React UI components, Next.js configuration, and Cloudflare Workers setup, zero evidence of MCP server scaffolding (no mcp package, no tool registration, no protocol handlers).
MCP API route handler providing pagination and search functionality for MCP items
Recommendation API route handler providing LLM-based MCP recommendations based on user queries
Not an MCP server. Codebase is a Next.js web application with HTTP API routes, not an MCP protocol implementation. No mcp package, no tool registration, no MCP handlers detected.
Tool names lack action verbs. 'GET /api/mcp' and 'POST /api/recommend' are HTTP routes, not verb_noun tool names. Should be 'search_mcp_items' and 'get_mcp_recommendations'.
Input schemas lack type constraints and validation. 'query' and 'page' parameters have basic type info but no enums, min/max bounds, or format constraints. 'items' array has no item schema definition.
No output schemas documented. Responses are inferred from code comments but not formally specified. LLMs cannot plan downstream calls without knowing return field names and types.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 21 | 2026-07-28+ | v2 |
No error handling guidance. No recovery hints, error categorization, or actionable error messages visible in route handlers. Agents cannot self-correct on failures.