
Mcp Test
io.github.bharath-krishnaPublished by GitHub account bharath-krishnav0.1.0Updated Oct 24, 2026
A simple MCP server with an echo tool for testing purposes
Overview
A minimal local MCP test server that exposes a single echo tool returning any message sent to it.
- What you can do
- Echo a message: the assistant can send a text string and receive it back prefixed with Echo, confirming the connection works.
- When to use it
- Useful for checking that an MCP client is configured correctly, for trying out tool calls, or as a starting template for building your own server. It offers no real-world data or actions.
- Requirements
- Runs as a local process over stdio, installed from the PyPI package mcp-echo-server (for example with pip) and launched with the mcp-echo-server command. No accounts, API keys, headers or environment variables are declared.
Installation
In SourceWeft
- Open Mcp Test in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
MCP Test Server
mcp-name: io.github.bharath-krishna/mcp-test
A simple Model Context Protocol (MCP) server with an echo tool for testing purposes.
Features
- Echo Tool: Returns back any message you send to it
Installation
Usage
Add this server to your MCP client configuration:
Development
Install in development mode:
Tools
echo
Echoes back the provided message.
Input:
message(string, required): The message to echo back
Example:
Output:
Source: README.md at commit 0f9fe25
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.