No user-submitted related servers found.
Scored across 14 tools
Each tool has a clear, distinct purpose: connection lifecycle (connect, disconnect, status), introspection (list tools/resources/prompts), execution (call_tool, read_resource, get_prompt), and a few trivial test utilities (ping, echo, add). No two tools appear to do the same thing, and the descriptions reinforce their uniqueness.
The majority of tools follow a verb_noun pattern (e.g., list_tools, read_resource, connect_to_server), but there are exceptions like 'disconnect', 'ping', 'echo', and 'add' which are bare verbs or single nouns. This mix is noticeable, though the exceptions are trivial and arguably acceptable for test utilities.
At 14 tools, the server provides a comprehensive but focused surface for testing MCP interactions. The count includes both essential operations (connect, list, call, read) and a few trivial tools (ping, echo, add) that serve diagnostic purposes. It is not excessive for the stated goal of an MCP test server.
The tool set covers the full lifecycle of interacting with an MCP server: connection management, introspection of all primitives (tools, resources, prompts), execution of each type, and a high-level workflow (execute_prompt_with_llm). Missing operations like resource update/delete are not typically required for a test harness, so the surface is sufficiently complete.