Fetch API 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| requestD | – |
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 ambiguity or overlap between tools. The single tool 'request' stands alone with no other tools to confuse it with.
A single tool inherently has perfect naming consistency, as there are no other tool names to compare it against. The name 'request' is clear and follows no conflicting patterns.
A single tool for an API server is too few for the apparent scope, as typical API interactions require multiple operations like GET, POST, PUT, DELETE. This minimal set is insufficient for comprehensive coverage.
The tool surface is severely incomplete for an API server domain. With only a generic 'request' tool and no descriptions, it lacks specific operations (e.g., for different HTTP methods or endpoints), making it impossible to perform standard CRUD workflows.