Skip to main content
Glama
Auxin-io

Hello World MCP Server

by Auxin-io
README.md
# ๐Ÿง  Demo MCP Server with Smithery

This repository showcases a demo implementation of a **Model Context Protocol (MCP)** server using **Smithery**, designed to help AI agents interact with tools securely and efficiently.

It includes a streamable MCP server that generates a simple Python "Hello World" program and is ready for integration with LibreChat.

---

## ๐Ÿ“ฆ Project Structure

File Structure
Demo-MCP-Server-Smithery/ 
โ”œโ”€โ”€ safe-mcp-server/ # Secure MCP server using Smithery CLI 
โ”œโ”€โ”€ insecure-python-code/ # Example of insecure code for contrast 
โ”œโ”€โ”€ smithery.yaml # Smithery configuration file 
โ””โ”€โ”€ README.md # You're reading it!

## ๐Ÿš€ Features

- **Secure MCP Server**: Built with Smithery CLI to ensure safe tool interactions.
- **Insecure Code Samples**: Included for educational contrast and security awareness.
- **LibreChat Integration**: Ready to plug into LibreChat for AI agent communication.
- **Streamable Output**: Generates and streams a basic Python script.

---

## ๐Ÿ› ๏ธ Requirements

- Node.js and npm
- Smithery CLI installed
- LibreChat (optional for integration)

---

## ๐Ÿงช Getting Started

1. Clone the repository:
   ```bash
   git clone https://github.com/Auxin-io/Demo-MCP-Server-Smithery.git
   cd Demo-MCP-Server-Smithery

2. Install dependencies (if applicable).

3. Run the secure MCP server:
cd safe-mcp-server
smithery run smithery.yaml

4. Test the output and explore the insecure code for comparison.


๐Ÿง‘โ€๐Ÿ’ป Contributing
Pull requests are welcome! Feel free to fork the repo and submit improvements or new features.

๐Ÿ“„ License
This project is licensed under the MIT License.

โœจ Acknowledgments

Learn More
Smithery Documentation
LibreChat GitHub

๐Ÿง‘โ€๐Ÿ’ป Contributing
Pull requests are welcome! Feel free to fork the repo and submit improvements or new features.

TDQS

C2.4/5.0

Scored across 1 tool

Disambiguation5/5

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 single tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tool names to compare it with. The name 'Secure-Agent-MCP' stands alone without any conflicting patterns or styles.

Tool Count2/5

A single tool is too few for most server purposes, making it feel thin and limiting functionality. While it might suffice for a minimal 'Hello World' example, it lacks the breadth expected for practical agent interactions in typical domains.

Completeness1/5

The server is severely incomplete; with only one tool that returns a simple message, there is no coverage of any meaningful domain or lifecycle operations. It fails to provide a usable surface for agents to perform tasks beyond a trivial response.

Maintenance

ActivityInactive
ResponsivenessNo issues