This is a spec-checking CLI tool, not an MCP server. The two 'echo' tools in ref-servers/old-server.ts are test fixtures for the conformance probe, not production tools. Both tools have identical names ('echo'), identical descriptions ('Returns a fixed greeting; a tools/list + tools/call fixture.'), and empty input schemas ({}). The tool definitions are minimal test stubs, not real implementations. The codebase is a readiness checker for OTHER servers, not a server itself. Scoring reflects the fixture nature: naming is generic, descriptions are test-oriented, and schemas are absent.

• Replace duplicate 'echo' tools with distinct names reflecting their purpose (e.g., 'echo_greeting', 'echo_fixture').
• Add explicit JSON Schema definitions: { type: 'object', properties: {}, required: [], description: 'No parameters required.' }
• Rewrite descriptions for clarity: 'Returns a fixed greeting message. Use this to test tool invocation and response handling.' (instead of test-fixture language).
• If these are intentionally test fixtures, document them as such in comments and consider moving them to a separate test-only module.
• For production use, add meaningful tools that demonstrate the server's actual capabilities (e.g., 'get_server_info', 'validate_spec_compliance').

Inferred effective spec: 2026-07-28+.

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained