McProxy
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Returns a simple pong response. Used to verify the MCP server is running. Read-only. |
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 a single tool, there is no possibility of confusion between tools. The ping tool's purpose is clearly stated as a health check.
The single tool name 'ping' is a clear, conventional verb that matches its read-only health-check function. With one tool there is no pattern inconsistency to penalize.
A server named McProxy with only one health-check tool feels far too thin for its apparent scope. A proxy server would typically expose multiple operational tools, making one tool insufficient.
The tool surface provides only liveness verification and no actual proxy functionality, which is severely incomplete given the server name. Agents expecting proxy capabilities would hit a dead end immediately.