ProxyShield MCP
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 |
|---|---|
| route_requestC | Determines whether an HTTP request should use residential, datacenter, or direct connection to optimize cost. |
| classify_assetA | Checks if a URL points to a heavy static asset (image, font, video, stylesheet) that can bypass residential proxies. |
| get_evasion_headersB | Returns rotating anti-detection browser headers (User-Agent, Sec-CH-UA, viewport specifications). |
| record_metricB | Records bytes transferred and tier used to calculate cumulative bandwidth and cost savings. |
| get_bandwidth_savingsB | Returns total bandwidth redirected away from expensive residential proxies and cumulative USD saved. |
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 5 tools
Each tool has a distinct purpose: routing decisions, asset classification, header generation, metric recording, and savings reporting. route_request and classify_asset both touch routing logic and could be momentarily confused, but their descriptions clearly delineate a decision tool versus an asset-type check.
All five tools follow a consistent verb_noun snake_case pattern (route_request, classify_asset, get_evasion_headers, record_metric, get_bandwidth_savings). No mixed conventions or stylistic deviations.
Five tools is well-scoped for a proxy cost-optimization domain, with each tool earning its place across routing, classification, headers, recording, and reporting. No redundancy or padding.
The surface covers the core lifecycle: decide routing, classify assets, fetch headers, record usage, and report savings. Minor gaps exist, such as resetting metrics or listing/configuring available proxy tiers, but agents can work around these.