mcp-http-request
Related Servers
Alternatives to mcp-http-request
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceAn MCP server that enables LLMs to make arbitrary HTTP requests (GET, POST, PUT, DELETE, etc.) with custom headers, bodies, and cookies, supporting JSON and error handling.12-
- AlicenseNot gradedqualityDmaintenanceA stateless MCP server that provides a configurable HTTP client tool for LLM agents, supporting custom methods, headers, bodies, timeouts, redirects, response size limits, DNS overrides, and TLS verification.MIT
- FlicenseAqualityDmaintenanceProvides a generic HTTP client tool allowing AI agents to make arbitrary HTTP requests from their environment, with support for environment-variable placeholders for secrets.1-
- AlicenseAqualityDmaintenanceEnables AI agents to send HTTP requests to any endpoint with full control over methods, headers, query parameters, and request bodies.120 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables testing and interacting with any REST API endpoint directly from MCP clients like Claude and Cline. Supports GET, POST, PUT, DELETE, and PATCH requests with configurable authentication (Basic, Bearer, API Key), custom headers, SSL verification control, and response size limits.5 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables users to test and interact with any REST API endpoints directly from their development environment through MCP clients such as Claude and Cline. Supports GET, POST, PUT, DELETE, and PATCH requests with configurable authentication, custom headers, SSL verification, and response size limits.5 npmISC
TDQS
Scored across 2 tools
fetch_text and http_request serve clearly distinct purposes: one extracts clean text from HTML pages, the other is a general HTTP client returning full response details. There is no ambiguity in selecting between them.
Both tool names follow a consistent snake_case verb_noun pattern: fetch_text and http_request. This pattern is predictable and clear.
With only 2 tools, the set is slightly minimal but still appropriate for the server's focused purpose of HTTP requests and text extraction. It covers the core needs without bloat.
The tools cover the essential HTTP methods and provide a specialized text extraction feature. Minor gaps like file uploads or streaming exist, but for the stated purpose of 'HTTP requests' and 'fetching text', the surface is reasonably complete.