Public MCP Server
# Public MCP Server
A Model Context Protocol (MCP) server implementation.
## Installation
### Using uvx (Recommended)
The easiest way to install and run this MCP server is using `uvx`:
```json
{
"public-mcp": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/Pankhur/public-mcp.git",
"mcp-server"
]
}
}
```
You can add this configuration to your project or Claude Desktop config to use this MCP server.
### Manual Installation
1. **Clone the repository**
```bash
git clone https://github.com/Pankhur/public-mcp.git
cd public-mcp
```
2. **Install dependencies**
```bash
pip install -e .
```
Alternatively, you can install dependencies using `uv`:
```bash
pip install uv
uv pip install -e .
```
## Usage
After installation, you can run the server with:
```bash
python -m mcpserver
```
## Development
To contribute to this project:
1. Fork the repository
2. Create a feature branch (`git checkout -b feature/amazing-feature`)
3. Commit your changes (`git commit -m 'Add some amazing feature'`)
4. Push to the branch (`git push origin feature/amazing-feature`)
5. Open a Pull RequestTDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it against. The tool's purpose is singular and clear.
Since there is only one tool, naming consistency is inherently perfect; there are no other names to be inconsistent with. The tool name 'add' is simple and follows a verb-only pattern, which is acceptable for a single tool.
A single tool is generally too few for most server purposes, as it limits functionality and suggests an incomplete or trivial scope. For a server named 'Public MCP Server', which implies broader utility, one tool is insufficient and mismatched.
The server's domain is unclear from the name and single tool, but a tool that only adds two numbers is severely incomplete for any plausible public utility purpose. There are obvious gaps, such as missing other arithmetic operations or broader functionalities.