Skip to main content
Glama
Sign In
ProxyShield MCP

ProxyShield MCP

by johannschiffer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ProxyShield MCP

No user-submitted related servers found.

    Related Servers

    • Camoufox Unified MCP Server

      tom613951
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to perform stealth browser automation and anti-detection web interaction, including session management, humanized interactions, and bypassing anti-bot/WAF protections.
      MIT

    • Proxy4Agent

      Goldentrii
      A
      license
      Not graded
      quality
      D
      maintenance
      Routes AI agent HTTP requests through residential proxies to bypass anti-bot systems, geo-target by country/city, and maintain sticky sessions across multi-step workflows.
      15 npm
      1
      MIT

    • puppeteer-real-browser-mcp

      eikaramba
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants with powerful, detection-resistant browser automation capabilities, allowing them to control a real web browser to navigate, extract content, and perform tasks while avoiding bot detection.
      9 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 5 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Resources