GRACE Hello MCP

io.github.rajitharulPublished by GitHub account rajitharulv1.0.0Updated Oct 24, 2026

A very simple remote MCP server that greets you, with a custom icon.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Server details

Identifier: io.github.rajitharul/grace-hello-mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account rajitharul for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.rajitharul%2Fgrace-hello-mcp.svg)](https://sourceweft.com/mcp/io.github.rajitharul%2Fgrace-hello-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A minimal remote MCP server that exposes one greeting tool, say_hello, and advertises a custom icon per the MCP spec.

What you can do: Greeting: one tool, say_hello, that returns a greeting, optionally addressed to a named person.
Server metadata: advertises a custom PNG icon in the initialize response's serverInfo.icons and on the tool.
Hosting extras: serves a landing/health page and the icon file alongside the MCP endpoint.
When to use it: Useful as a smoke test or reference example for connecting a client to a remote Streamable HTTP MCP server, or for checking how a client renders spec-advertised server icons. It offers no real work beyond a greeting.
Requirements: A remote Streamable HTTP endpoint; no authentication, environment variables or headers are declared. The hosted instance runs on Render's free plan, which sleeps on idle, so the first request after a pause may take around 30 seconds to wake.

Before you install

Icon display depends on the client: the README notes Claude Code and Claude Desktop currently show a default placeholder for third-party servers. The hosted free instance may be slow to respond after idling. No credentials are requested.

Installation

In SourceWeft

Open GRACE Hello MCP in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.rajitharul%2Fgrace-hello-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "grace-hello": {
      "type": "http",
      "url": "https://grace-hello-mcp.onrender.com/mcp"
    }
  }
}

README

GRACE Hello MCP

A very simple remote MCP server (Streamable HTTP transport) that advertises a custom icon per the MCP spec (rev 2025-11-25, SEP-973), ready to deploy on Render.

It exposes one tool, say_hello, and serves a custom PNG icon that is advertised in the initialize response's serverInfo.icons.

Project layout

File	Purpose
`server.js`	The MCP server (Express + `@modelcontextprotocol/sdk`, Streamable HTTP).
`make_icon.py`	Generates `static/icon.png` (stdlib only, no deps). Edit to change the icon.
`static/icon.png`	The icon that gets advertised + served.
`render.yaml`	Render blueprint for one-click deploy.

Run locally

Landing/health page (shows the icon): http://localhost:3000/
MCP endpoint: http://localhost:3000/mcp
Icon: http://localhost:3000/icon.png

Quick smoke test:

bash

curl -s -X POST http://localhost:3000/mcp \  -H 'Content-Type: application/json' \  -H 'Accept: application/json, text/event-stream' \  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'

curl -s -X POST http://localhost:3000/mcp \  -H 'Content-Type: application/json' \  -H 'Accept: application/json, text/event-stream' \  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'

You should see serverInfo.icons in the response.

Or use the official MCP Inspector (renders the icon):

Deploy on Render

Push this folder to a GitHub repo.
In Render: New ➜ Blueprint, point it at the repo. It reads render.yaml and creates a free Node web service. (Or New ➜ Web Service manually: build npm install, start npm start.)
Render injects RENDER_EXTERNAL_URL automatically, so server.js builds the correct absolute https://<your-service>.onrender.com/icon.png icon URL — no manual env vars needed.
Your MCP endpoint is https://<your-service>.onrender.com/mcp.

Note: Render's free plan sleeps on idle, so the first request after a while may take ~30s to wake.

Add it to an MCP client

Claude Code (CLI):

Then in a session: /mcp to see it, and ask Claude to "use say_hello to greet Rajith".

Claude Desktop / other GUI clients: add a remote/HTTP MCP server pointing at https://<your-service>.onrender.com/mcp.

About the icon (read this)

This server advertises its icon correctly per the MCP spec: the icons array appears on serverInfo (and on the tool). It must be an https:// or data: URI — we use the hosted https://.../icon.png.

Whether a client shows it is up to that client. Icon rendering is a newer, inconsistently-supported feature:

✅ MCP Inspector and other spec-aware clients read and display it.
⚠️ Claude Code / Claude Desktop currently still show their default placeholder for arbitrary third-party servers — the branded icons in Claude's marketplace are first-party integrations configured on Anthropic's side. As client icon support matures, this server is already compliant and will "just work" with no changes.

Customize

Icon: edit colors/shapes in make_icon.py, then npm run make-icon (regenerates static/icon.png). Or just drop your own 512×512 PNG at static/icon.png.
Tools: add more setRequestHandler cases / tool definitions in server.js.

Source: README.md at commit c4ae4bf

Tools

SourceWeft has not read this server's tools yet.

Version history

v1.0.0LatestSep 16, 2026

Score

75% 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 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 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.