Web Request 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| http_requestA | Execute an HTTP request with custom method, URL, headers, and body. Supports GET, POST, PUT, DELETE, PATCH, and other HTTP methods. The AI can choose all parameters based on the task requirements. |
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
Only one tool exists, so there is no ambiguity. The tool's purpose is clearly defined for HTTP requests.
With a single tool, naming consistency is not applicable but trivially consistent. The name 'http_request' is clear and follows a common pattern.
The server has only one tool, which is minimal but arguably sufficient given the broad scope of HTTP requests it supports. It is slightly under but reasonable.
The tool covers all standard HTTP methods and allows custom headers and body, making it fairly complete for basic web requests. However, it may lack support for advanced features like cookie handling or redirect following.