my-mcp-server
Related Servers
Alternatives to my-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceA boilerplate for building MCP servers using TypeScript, with example tools like calculator and greet, plus resource support.6-
- FlicenseNot gradedqualityDmaintenanceA boilerplate project for quickly developing MCP servers with TypeScript, featuring example tools (calculator, greeting, time) and resources with Zod schema validation.-
- FlicenseNot gradedqualityDmaintenanceA boilerplate project for quickly developing MCP servers using TypeScript, featuring example implementations of tools (calculator, greetings) and resources (server info) with Zod schema validation.-
- FlicenseNot gradedqualityDmaintenanceA boilerplate project for quickly developing MCP servers using TypeScript SDK, with example implementations of calculator and greeting tools, plus resource handling capabilities.-
- FlicenseNot gradedqualityDmaintenanceA boilerplate project for quickly developing MCP servers using TypeScript SDK, featuring example tools (calculator, greeting) and resources with Zod schema validation.-
- FlicenseNot gradedqualityDmaintenanceA boilerplate project for quickly developing Model Context Protocol (MCP) servers using TypeScript, with example tools (calculator, greet) and resources (server info) pre-implemented.63 npm-
TDQS
Scored across 6 tools
Each tool addresses a completely different function (greeting, math, time, geocoding, weather, image generation), with no overlapping purposes. An agent will have no trouble selecting the correct tool.
Naming patterns are mixed: three tools use verb_noun with 'get-' prefix (get-time, get-weather, generate-image uses 'generate'), while 'calculator' is a noun and 'greet' is a bare verb. 'geocode' is a verb but not prefixed. The inconsistency is confusing but still readable.
With 6 tools covering distinct utilities, the count is appropriate for a general-purpose server. It is neither too sparse nor overloaded.
The tools cover basic functionalities in their respective areas, with complementary pairs (geocode + weather). While some missing utilities could be added, there are no critical gaps within the current scope.