HTTP MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_http_requestB | Send an HTTP request to any endpoint with custom headers, query parameters, and body |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clear and unambiguous.
The single tool follows a clear verb_noun convention, and the name accurately describes its function. Consistency is trivially maintained.
One tool is appropriate for a server dedicated solely to HTTP requests. While the count is below the typical range, it is not excessive or deficient for the narrow scope.
The tool supports full HTTP request customization, covering all methods and parameters. There are no obvious missing operations within the domain of making HTTP requests.