{
"mcpServers": {
"mcp-http-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Sample MCP HTTP server with a single hello world tool
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
MIT. View license →
Is it maintained?
Last commit 143 days ago.
Will it work with my client?
Transport: http. Compatibility not confirmed.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
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.