Search for:
Why this server?
This server is a 'minimal, dockerized template for creating HTTP-based Model Context Protocol servers', explicitly stating its use of HTTP transport and serving as a simple example.
Why this server?
This is a 'lightweight server implementation that exposes Python functions as discoverable tools via HTTP' clearly matching the 'simple example' and 'HTTP transport' criteria.
Why this server?
Described as a 'Python Flask-based Model Context Protocol server that provides basic tools... through stable HTTP endpoints', directly fulfilling the user's request for a simple example with HTTP transport.
Why this server?
This plugin is for 'building Model Context Protocol (MCP) servers with HTTP transport', making it a relevant example for demonstrating HTTP-based MCP.
Why this server?
Built with FastAPI, this server exposes endpoints via 'Model Context Protocol (MCP)' which inherently uses HTTP, serving as a practical example of HTTP transport.
Why this server?
As a 'comprehensive template for building Model Context Protocol (MCP) servers with FastMCP framework', it includes example tools and FastMCP is known to use HTTP transport.
Why this server?
This is a 'demonstration MCP server built with FastMCP v2.0 that provides basic mathematical calculations', and FastMCP typically uses HTTP transport, fitting the 'simple example' criteria.
Why this server?
This server explicitly supports 'both SSE and HTTP transports' and includes 'example tools for echoing messages and performing mathematical operations', making it a clear example of HTTP transport.
Why this server?
Described as a 'unified HTTP/HTTPS service that exposes Model Context Protocol (MCP) functionality over HTTP endpoints', this server clearly uses HTTP transport.
Why this server?
This is a 'stateless HTTP server implementing the Model Context Protocol' designed for simple interactions, directly matching the 'simple example' and 'HTTP transport' requirements.