MCP Server Starter
Related Servers
Alternatives to MCP Server Starter
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables building and running MCP servers from a single executable, with shared daemons, concurrency controls, retries, caching, security, and OpenAPI integration.MIT
- FlicenseNot gradedqualityCmaintenanceEnables deployment and connection to a minimal Streamable HTTP MCP server with bearer-token authentication, a health endpoint, and an example tool, while allowing developers to add custom tools.-
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients to call a hello tool and access observability features, including metrics and request traces, through a Streamable HTTP transport with SQLite-backed storage.-
- FlicenseNot gradedqualityCmaintenanceExposes the getWeather and getTime tools over a stateless streamable-HTTP MCP endpoint at /mcp, so clients can look up weather for a location and the current time for a timezone through MCP tool calls. Running the same pure tool code as the app's OpenAPI surface, it lets you register the deployment as a remote MCP tool and compare MCP against custom-OpenAPI integration.-
- AlicenseAqualityBmaintenanceEnables coding agents and MCP clients to expose typed tools and docs resources over stdio or secure Streamable HTTP, connect to REST backends, and ship through tested PyPI and Registry releases.31MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to discover and call three tools over Streamable HTTP: generating personalized greetings, retrieving the current ISO 8601 date/time in a configured timezone, and performing addition, subtraction, multiplication, or division with clear error handling. It runs locally or in Docker and exposes a health endpoint for monitoring.MIT
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of selecting the wrong one. The tool's purpose (current time in a given IANA zone) is clearly stated and non-overlapping with anything else on the server.
The lone name `time_in_zone` is descriptive snake_case and reads naturally. Consistency across a pattern cannot really be assessed with one tool, but nothing is inconsistent.
A single tool is a thin surface for anything beyond a hello-world scaffold, matching the 'starter' framing but offering little utility. It sits at the low end of the appropriate range.
The time domain is only minimally covered: there is no timezone conversion, no way to list supported zones, and no fallback for local/server time. Agents asking anything beyond 'what time is it in X' will hit a dead end.