The four tools operate on their own arguments and reach nothing else, so what you get is a server that answers — enough to confirm a client's transport, tool discovery and argument passing all work before anything real is connected. get_server_info is the piece you would keep and rewrite; say_hello, echo_message and count_words exist to be replaced.
A minimal example MCP server whose 4 tools — say_hello, echo_message, count_words and get_server_info — each act on the argument they are handed rather than on any outside system.
- echo_message returns the message you passed it, which is the shortest check that a client is reaching the server and handing arguments through unaltered.
- get_server_info takes no arguments and returns a dictionary describing this server.
- say_hello takes a name and returns a greeting for it; count_words takes a text and returns its word count.
No account and no key. Each call is self-contained: say_hello needs a name, echo_message a message, count_words a text, and get_server_info nothing at all.
One command — uvx --from git+https://github.com/macsymwang/hello-mcp-server.git hello-mcp-server