MCP API Requester
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 |
|---|---|
| make_requestA | Make an arbitrary HTTP request (GET, POST, PUT, DELETE, etc.) with custom headers and body. Returns the status, headers, and body of the response. |
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 possibility of confusion or overlapping purposes. The single tool's purpose is clearly defined as making arbitrary HTTP requests.
With a single tool named 'make_request', the naming follows a clear verb_noun pattern. There are no other tools to create inconsistency.
The server has just one tool, which is slightly below the typical 3-15 range, but for a focused HTTP request utility this is reasonable. The tool is general-purpose and well-suited to the server's stated purpose.
The single tool covers the full scope of making HTTP requests: all methods, custom headers, body, and returns status, headers, and body. There are no obvious gaps in the server's intended functionality.