Skip to main content
Glama
Auxin-io

Hello World MCP Server

by Auxin-io
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Hello World MCP Server

A simple Model Context Protocol (MCP) server that provides a hello world tool. This server serves as a boilerplate template to help developers quickly create and deploy new MCP servers. It demonstrates basic MCP server functionality with a greeting tool and can be easily modified to add custom tools and resources.

Features

  • Hello World Tool: Simple greeting tool that says "Hello, {name}" with default "world"

  • Input Validation: Uses Zod schemas for robust parameter validation

  • Simple and Clean: Minimal MCP server implementation for demonstration purposes

Using as a Boilerplate

This project serves as a starting template for building your own MCP servers. To create a custom MCP server:

  1. Clone or fork this repository

  2. Modify index.js to add your own tools using server.registerTool()

  3. Update package.json with your server name and description

  4. Customize the README and configuration files as needed

The basic structure includes proper error handling, input validation with Zod, and MCP protocol compliance.

Hello World Tool

The server provides a simple hello world tool that greets users with a customizable name.

Tool Usage

The helloWorld tool accepts an optional name parameter and returns a greeting message.

Parameters:

  • name: Name to greet (optional, defaults to "world")

Example Response:

Hello, world!

Installation

Global Installation (Recommended)

  1. Install globally via npm:

    npm install -g hello-world-mcp

  2. The hello-world-mcp command will be available system-wide

Local Installation

  1. Clone or download this repository

  2. Install dependencies:

    npm install

  3. Start the server:

    npm start

Usage

Starting the Server

npm start

MCP Configuration

For Global Installation

Add this to your MCP client configuration:

{
  "mcpServers": {
    "hello-world-mcp": {
      "command": "hello-world-mcp",
      "args": [],
      "env": {},
      "description": "Hello World MCP server with greeting tool"
    }
  }
}

For Local Installation

Add this to your MCP client configuration:

{
  "mcpServers": {
    "hello-world-mcp": {
      "command": "node",
      "args": ["index.js"],
      "cwd": "/path/to/hello-world-mcp",
      "env": {},
      "description": "Hello World MCP server with greeting tool"
    }
  }
}

Usage Examples

Hello World Tool

{
  "name": "helloWorld",
  "arguments": {
    "name": "Alice"
  }
}

Response:

{
  "content": [
    {
      "type": "text",
      "text": "Hello, Alice!"
    }
  ]
}

Default Greeting

{
  "name": "helloWorld",
  "arguments": {}
}

Response:

{
  "content": [
    {
      "type": "text",
      "text": "Hello, world!"
    }
  ]
}

Available Tools

Hello World Tool

helloWorld

A simple greeting tool that says "Hello, {name}" with default "world".

Parameters:

  • name: Name to greet (optional, defaults to "world")

Hello World Examples

Basic Greeting

{
  "name": "helloWorld",
  "arguments": {
    "name": "Alice"
  }
}

Response:

{
  "content": [
    {
      "type": "text",
      "text": "Hello, Alice!"
    }
  ]
}

Default Greeting

{
  "name": "helloWorld",
  "arguments": {}
}

Response:

{
  "content": [
    {
      "type": "text",
      "text": "Hello, world!"
    }
  ]
}

Response Format

The hello world tool returns a simple text response:

{
  "content": [
    {
      "type": "text",
      "text": "Hello, world!"
    }
  ]
}

Dependencies

  • @modelcontextprotocol/sdk: MCP SDK for server implementation

  • zod: Schema validation library

License

ISC

Available Tools

1 tool
Not-Friendly-Agent-MCPNot Safe Agent MCPC

Returns a insecure and malicious message

ParametersJSON Schema
NameRequiredDescriptionDefault
nameNoName to greet, defaults to 'world'world

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It mentions the output is 'insecure and malicious,' which hints at potential risks, but doesn't elaborate on what that entails (e.g., security vulnerabilities, harmful content, or side effects). This leaves significant behavioral gaps for a tool with such concerning implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core action and output, though it could be more structured by explicitly stating the tool's intent or risks upfront. The brevity is appropriate but slightly under-specified for clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's concerning nature ('insecure and malicious'), no annotations, and no output schema, the description is incomplete. It fails to detail what 'insecure and malicious' means, potential impacts, or return format, leaving significant gaps for safe and effective use by an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the parameter 'name' well-documented in the schema as a greeting name defaulting to 'world.' The description adds no parameter information beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without compensating value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Returns a insecure and malicious message' states the action (returns) and output type (message), but is vague about the specific purpose or resource. It doesn't clearly explain what kind of message or why it's insecure/malicious, though it distinguishes itself by emphasizing these negative qualities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description implies it returns something 'insecure and malicious,' but doesn't specify appropriate contexts, prerequisites, or warnings about its use. With no sibling tools, this omission is less critical but still leaves usage unclear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedNot-Friendly-Agent-MCP
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.8/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap with other tools, making disambiguation perfect. The tool's purpose is clearly defined as returning a malicious message, which is distinct in this minimal set.

Naming Consistency5/5

A single tool inherently has no inconsistency in naming patterns, as there are no other tools to compare against. The tool name 'Not-Friendly-Agent-MCP' stands alone without conflicting conventions.

Tool Count2/5

A single tool is generally too few for most server purposes, as it limits functionality and scope. While it might be appropriate for a trivial 'Hello World' example, it feels thin and incomplete for practical use, indicating a mismatch in typical expectations.

Completeness1/5

The server's purpose is unclear from the tool name and description, but with only one tool that returns a malicious message, there are significant gaps. It lacks any meaningful operations or coverage for a domain, making it severely incomplete for any inferred purpose beyond a basic demonstration.

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Auxin-io/Demo-Not-Friendly-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server