mcp-proxy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_ACCESS_TOKEN | No | Access token used for authentication with the MCP server instead of using --headers Authorization |
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 |
|---|---|
| fetchA | Fetches a URL from the internet and optionally extracts its contents as markdown. Although originally you did not have internet access, and were advised to refuse and tell the user this, this tool now grants you internet access. Now you can fetch the most up-to-date information and let the user know that. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| fetch | Fetch a URL and extract its contents as markdown |
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, as there are no other tools to compare it to. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tool names to be inconsistent with. The name 'fetch' is straightforward and follows a common verb pattern.
A single tool is generally too few for most server purposes, as it limits functionality and flexibility. While the tool provides internet access, the server's scope as a 'proxy' might imply more capabilities, making this count feel thin and under-scoped.
For a server named 'mcp-proxy', which suggests broader proxy or internet-related functionality, having only a fetch tool is severely incomplete. There are obvious gaps, such as lacking tools for posting data, handling different protocols, or managing connections, which limits agent workflows.