mcp-starter
Related Servers
Alternatives to mcp-starter
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceFastAPI Todo API with an MCP server for managing todos, deployable to Render, AWS App Runner, or ECS.-
- FlicenseNot gradedqualityBmaintenanceA simple MCP server for managing a todo list — add tasks, list tasks, and mark tasks complete. Built with the Python MCP SDK (FastMCP) as a hands-on learning project.-
- FlicenseBqualityDmaintenanceA template and demonstration project for building, testing, and deploying remote MCP servers using FastMCP and uv. It provides a foundational structure for creating MCP-compliant tools that can be hosted publicly and integrated with LLM agents.2-
- AlicenseNot gradedqualityDmaintenanceA multi-node todo application server using MCP protocol, Redis for storage, and OpenRouter for AI-powered prioritization analysis.MIT
- FlicenseNot gradedqualityBmaintenanceA minimal Python MCP Todo server backed by Appwrite Cloud, providing tools to add, list, get, update, complete, and delete tasks.-
- AlicenseNot gradedqualityCmaintenanceA demo MCP server exposing an in-memory todo list via tools (add_task, list_tasks, complete_task), a resource, and a prompt, over both stdio and HTTP transports.0ISC
TDQS
Scored across 1 tool
With only one tool, there is no possibility of inter-tool confusion or misselection. However, the complete absence of a description leaves some uncertainty about the tool's exact purpose and usage, slightly reducing clarity.
The single tool name 'greet' is a simple verb in lowercase, which is consistent with common MCP naming conventions. There is no second tool to create a naming pattern conflict.
A single, undocumented 'greet' tool is an extreme mismatch for any meaningful server scope. The rubric explicitly treats a single trivial tool as a score of 1.
The server provides no lifecycle, CRUD, or domain-specific operations beyond a trivial greeting. This is a severely incomplete surface for any practical agent use case.