MCP-BOS
Related Servers
Alternatives to MCP-BOS
No user-submitted related servers found.
Related Servers
- 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-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for Claude Desktop that provides structured memory management across chat sessions, allowing Claude to maintain context and build a knowledge base within project directories.6 npm6MIT
- AlicenseNot gradedqualityBmaintenanceA Python framework for building MCP servers that makes it simple to expose application data and actions to AI clients like Claude Desktop, Cursor, and VS Code through the Model Context Protocol. It wraps protocol handling behind a clean, decorator-based API allowing focus on business logic.23 PyPI1MIT
- AlicenseNot gradedqualityDmaintenanceA production-ready Model Context Protocol server that provides comprehensive file system management capabilities for seamless integration with Claude Desktop.1MIT
- FlicenseDqualityDmaintenanceA server built on mcp-framework that enables integration with Claude Desktop through the Model Context Protocol.11-
- FlicenseNot gradedqualityFmaintenanceA Model Context Protocol server that extends AI capabilities by providing file system access and management functionalities to Claude or other AI assistants.212 npm5-
TDQS
Scored across 4 tools
The tools are highly ambiguous and overlapping in purpose. 'add' performs arithmetic, 'hello' returns a greeting, 'my_tool' is described only as 'custom tool' with no clear purpose, and 'server_info' retrieves server metadata. 'my_tool' is completely undefined, making it impossible to distinguish from others, and the set lacks clear domain boundaries, leading to high misselection risk.
Naming is inconsistent with mixed conventions. 'add' and 'hello' use simple verb forms, 'my_tool' uses a vague noun phrase, and 'server_info' uses a noun_verb pattern. There is no predictable naming scheme across the set, though all names are readable in English.
With only 4 tools, the count feels too thin for any coherent domain. The tools span arithmetic, greetings, an undefined custom function, and server metadata, suggesting a poorly scoped utility set rather than a focused server purpose. This minimal count does not adequately cover a meaningful operational surface.
The tool set is severely incomplete for any inferable domain. If interpreted as a general utility server, it lacks basic operations like subtraction, multiplication, or data processing. The inclusion of 'my_tool' without description creates a dead end, and there are significant gaps that will cause agent failures due to missing core functionalities.