mcp-http
Related Servers
Alternatives to mcp-http
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to send HTTP requests to any endpoint with full control over methods, headers, query parameters, and request bodies.19 npmMIT
- FlicenseAqualityDmaintenanceUniversal HTTP client tool for LLM agents. Enables Claude and other MCP-compatible agents to perform GET, POST, PUT, DELETE, and other HTTP requests to any URL, including localhost and internal network addresses.2-
- AlicenseNot gradedqualityCmaintenanceEnables LLMs to make arbitrary HTTP API requests with any method and full control over headers, query parameters, and body.4 npmISC
- AlicenseBqualityDmaintenanceEnables automatic HTTP requests (GET, POST, PUT, DELETE, etc.) with JSON validation and proxy support. Supports custom headers, request bodies, and environment variable configuration for seamless API integration.14 npmMIT
- AlicenseAqualityAmaintenanceEnables LLMs to make HTTP requests using structured cURL commands with support for multiple authentication methods, custom headers, and comprehensive request/response control.27 npm3MIT
- AlicenseNot gradedqualityCmaintenanceProvides a structured HTTP client tool for making web requests with full HTTP method support, detailed response metadata, and error handling. Enables AI assistants to interact with any web API or endpoint through the curl_request tool.8 npm2MIT
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusion or overlapping purposes. The http_request tool has a clear, distinct role as a generic HTTP client.
The tool name 'http_request' is a clear verb_noun pattern. Since there is only one tool, consistency is trivially maintained, and the name accurately reflects its function.
While a single tool feels thin, it is justified for a focused HTTP client server. The tool is comprehensive and not trivial, but the server offers no additional utilities or convenience wrappers.
The http_request tool supports all common HTTP methods, headers, query parameters, and body payloads, and returns status, headers, and body content. This fully covers the expected domain of an HTTP client with no obvious gaps.