My UV MCP Server
Related Servers
Alternatives to My UV MCP Server
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityCmaintenanceA simple MCP server that provides a 'hello' tool to return a personalized greeting, demonstrating integration with Claude Desktop.-
- FlicenseNot gradedqualityBmaintenanceA lightweight MCP server that bridges Claude AI with local Python execution, enabling personalized greetings and demonstrating local tool integration.-
- AlicenseAqualityDmaintenanceA getting started guide and template for creating Python-based MCP servers using uv for project management. Provides setup instructions for developing and testing MCP tools that can integrate with Claude Desktop.11MIT
- AlicenseAqualityCmaintenanceA demonstration MCP server for local development and testing with Claude Desktop on WSL. Provides basic utility tools including greeting messages, echo functionality, and server information retrieval.3MIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server that connects Claude Desktop to execute custom local code, such as generating custom greetings.2 npmISC
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server built with the mcp-framework for developing and managing custom tools. It provides a structured foundation for building and integrating modular components like data processors and API clients into Claude Desktop.2 npm-
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'add_numbers' has a single, clearly defined purpose that cannot be confused with any other tool in this set.
The single tool name 'add_numbers' follows a clear verb_noun pattern, and with only one tool, there is no inconsistency to evaluate. The naming is straightforward and predictable in isolation.
A single tool is too few for most practical server purposes, as it severely limits functionality and scope. This feels thin and inadequate for handling any meaningful domain beyond a trivial operation, indicating a poor fit for typical MCP server use cases.
The server's purpose is unclear from the single tool, making it impossible to assess coverage meaningfully. With only a basic arithmetic operation, there are significant gaps in any plausible domain, rendering the tool surface severely incomplete for practical agent workflows.