This is a scaffolding CLI tool, not a functioning MCP server. The two tools (echo, get_time) are templates embedded in string literals within src/templates/javascript/server.js.ts and src/templates/typescript/server.ts.ts. Tool definitions are INFERRED from template strings, not directly registered in executable code. Additionally, the templates contain bugs (HttpServerTransport is undefined; it should be StdioServerTransport per the imports) and lack error categorization, recovery guidance, and actionable error messages.
Echoes back the input text
Returns the current server time
Tool definitions are inferred from template strings, not directly registered in executable code. Cannot verify actual runtime behavior or schema enforcement.
This is a scaffolding generator tool, not a production MCP server. The evaluated tools are example templates, not the actual tool being delivered.
Generated template code contains a bug: HttpServerTransport is imported but not defined in the SDK. Code uses StdioServerTransport import but attempts HttpServerTransport instantiation. This will fail at runtime.
Error responses in template ('Unknown tool', 'Unknown resource') do not provide recovery guidance. Missing pattern:recovery-guide implementation.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 50 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 35 | - | v1 |
No error categorization (retryable vs user-fixable vs fatal). Agents cannot determine next action on failure.
'get_time' description is minimal (40 chars). Does not explain use case, when to call vs alternatives, or what the returned format is.
'echo' tool is trivial (no practical use in agent workflows) and lacks guidance on idempotency or safe retry semantics.
Output schemas are not documented. LLMs cannot plan downstream tool calls without knowing response structure. Only response format is visible in the code (text content), not formalized in a schema declaration.