Sample MCP HTTP server with a single hello world tool
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"mcp-http-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Sample implementation of a Model Context Protocol (MCP) HTTP server built with ASP.NET Core minimal APIs. It exposes a single hello_world tool to demonstrate tool registration, discovery, and execution with stream-friendly JSON responses.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in developer-tools
Manage Supabase projects — databases, auth, storage, and edge functions
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
MCP Security Weekly
Get CVE alerts and security updates for Mcp Http Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Sample implementation of a Model Context Protocol (MCP) HTTP server built with ASP.NET Core minimal APIs. It exposes a single hello_world tool to demonstrate tool registration, discovery, and execution with stream-friendly JSON responses.
# Restore dependencies
cd c:/s/AI/mcp-http-server
dotnet restore
# Run the server (HTTPS by default)
dotnet run --project src/McpHttpServer/McpHttpServer.csproj
The service listens on both HTTP and HTTPS endpoints defined in Properties/launchSettings.json and supports JSON-RPC requests at /.
curl http://localhost:5248/tools
Sample response:
{
"tools": [
{
"name": "hello_world",
"description": "Returns a friendly greeting. Provide an optional 'name' field in the input.",
"inputSchema": {
"type": "object",
"title": "HelloWorldInput",
"additionalProperties": false,
"properties": {
"name": {
"type": "string",
"description": "Optional name to include in the greeting."
}
}
}
}
]
}
curl https://localhost:7272/mcp/execute `
-H "Content-Type: application/json" `
-d '{"tool":"hello_world","input":{"name":"Azure"}}' `
-k
The server streams the JSON response to the caller:
{"tool":"hello_world","contentType":"application/json","result":{"message":"Hello, Azure!"}}
VS Code and other MCP-aware clients can communicate with the server via JSON-RPC 2.0 on the root endpoint:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "hello_world",
"arguments": {
"name": "Azure"
}
}
}
The server replies with:
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"tool": "hello_world",
"content": [
{
"type": "json",
"json": {
"message": "Hello, Azure!"
}
}
]
}
}
# Run integration tests
dotnet test
# Format the codebase (requires dotnet-format global tool)
dotnet format
IMcpTool and adding them to the DI container.