A lightweight MCP management platform designed for independent developers
MCP Hub Lite provides 7 system tools for server management with explicit schemas and descriptions. All tools have input schemas with typed properties and descriptions. However, descriptions are brief (10-50 chars), parameter descriptions lack detail on constraints/formats, and output schemas are not documented. Tool naming follows verb_noun convention (list_, get_, call_, search_, update_). No error handling guidance or recovery patterns visible. Composition is reasonable, tools are single-purpose and chainable via serverName/toolName references. Security concern: call_tool accepts arbitrary toolArgs without validation guidance.
Call a tool on the specified server
Get complete schema for a specific tool
List all connected MCP servers
List all instance tags for a specific MCP server
List all tools from the specified server
Search tools across all connected servers by name or description
Update the description of a connected server
Descriptions are too brief (10-50 chars). Rubric baseline is 194 chars. Descriptions lack WHEN to use, prerequisites, and return value guidance. Examples: 'List all connected MCP servers' (32 chars), 'List all instance tags for a specific MCP server' (48 chars).
Parameter descriptions are missing or minimal. 'serverName' has no description in list_tools; 'toolArgs' in call_tool lacks format/constraint guidance. Rubric requires every parameter to have a description explaining what it controls.
Output schemas are not documented. Rubric requires 100% of A+ tools to have documented return types. Callers cannot plan downstream tool calls without knowing what fields are returned.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | 2026-07-28+ | v2 |
call_tool accepts arbitrary 'toolArgs' object with no validation guidance. Rubric requires parameter descriptions to state expected format, range, and allowed values. No error handling guidance for invalid arguments.
No error handling or recovery guidance. Rubric requires error responses to tell the LLM what to do next and categorize errors as retryable/user-fixable/fatal. No visible error classification or recovery patterns.