Drag-and-drop MCP server scoping for Claude Code. REST + SSE FastAPI server for managing MCP server registrations, groups, deployments, and token budgets.
This is a registry/metadata server, not a traditional MCP tool server. The 6 endpoints are HTTP REST routes, not MCP tools with formal schemas. No tool definitions are visible in the source, tool names, descriptions, and parameters are inferred from FastAPI route handlers. Input schemas are absent; output schemas are undocumented. Descriptions exist but are minimal (10-50 chars). No parameter validation, error guidance, or structured output schemas. This server does not follow the MCP tool definition pattern and cannot be evaluated as a standard MCP tool server.
Return the registry HTML interface
Health check endpoint returning status, server count, and group count
Return the metadata catalog for all known MCP servers
Completeness scores for all servers in the catalog
Compute token budgets per server, per group, and combined. Returns unscoped, global, per-group budgets, scoped averages, and savings calculations.
Auto-enrich all servers from filesystem inspection
No formal MCP tool definitions. Routes are HTTP endpoints, not registered MCP tools with input/output schemas. Tool existence is inferred from FastAPI route handlers, not explicit tool registration.
No input schemas visible. Parameters (e.g., for POST /server-catalog/enrich) are defined as Pydantic models but not exposed as JSON Schema in tool definitions. LLMs cannot see parameter constraints.
Output schemas undocumented. Routes return JSON (e.g., /health returns {status, servers, groups}) but no schema is declared. LLMs cannot plan downstream tool calls or extract fields reliably.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 24 | 2026-07-28+ | v2 |
Minimal descriptions (10-50 chars). Descriptions like 'Return the registry HTML interface' and 'Health check endpoint returning status, server count, and group count' lack context for when/why to call. No guidance on prerequisites or next steps.
No error handling guidance. No recovery hints, error categorization, or actionable error messages. If /server-catalog returns 404, LLM has no guidance on what to do next.