Config-driven MCP server framework built on the official rmcp SDK. Fully implements the Model Context Protocol spec — define tools, auth, prompts, resources, and HTTP behavior in YAML/JSON with minimal Rust code.
The 'echo' tool in tests/e2e_tools.rs has a trivial definition with minimal practical value. Description is only 10 characters ('echo tool'), falling below the 20-character minimum threshold. Input schema is an empty object with no parameters defined, providing zero guidance to LLMs about what the tool accepts. No output schema is documented. The tool appears to be a test fixture rather than a production-grade tool. The framework itself (rust-mcp-core) is well-engineered with extensive features (auth, prompts, resources, HTTP hardening), but the single exposed tool fails basic quality standards.
echo tool
Tool description is 10 characters ('echo tool'), below 20-char minimum. Provides no context for LLM selection.
Input schema is empty object with no parameters. LLM cannot determine what arguments the tool accepts or their types.
No output schema documented. LLM cannot plan downstream operations or extract returned data.
Tool appears to be a test fixture (in tests/e2e_tools.rs) rather than a production tool. No real-world use case evident.
No error handling guidance. Tool does not indicate what happens on invalid input or how to recover.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 39 | 2025-06-18+ | v2 |