Working Proxy Sites

Search the provider database

search_providers

Read-only

Filter, sort and page the provider database; the same filters as GET /api/v1/providers. Returns {total, limit, offset, filters (as applied), warnings, providers}. Default listing_status is active and the default limit here is 20 (max 200). max_price is in each matching product's own price_unit (per GB, per IP…), so combine it with type and pricing_model. Product filters (pricing_model, max_price, min_countries, min_pool, targeting, country, rotation, unlimited_bandwidth) must all hold for the same product and never match unknown values, so they only match providers whose structured products are known; see warnings. Unknown prices, pools and country counts sort last.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Case-insensitive match on name, slug, alias, domain or legal entity.
`api`	No	Offers a self-service API.
`kyc`	No	Identity verification level.
`auth`	No	Proxy authentication method offered.
`sort`	No	Default "rank" (featured, community score, staff rank).
`type`	No	Proxy type sold.
`limit`	No	Default 20.
`order`	No	Default asc for price and name, desc otherwise.
`offset`	No
`country`	No	ISO 3166-1 alpha-2 code (e.g. "DE"): a product whose published country list (country_codes) includes it.
`payment`	No	Accepted payment method.
`min_pool`	No	Minimum advertised pool size in IPs.
`protocol`	No	Protocol supported (for the given type when type is set).
`rotation`	No	A product offering this rotation mode.
`max_price`	No	Maximum price_from_usd, in the matching product's price_unit. Use with type and pricing_model (units are canonical per model: per_gb GB, per_ip IP/month, per_port port/month).
`targeting`	No	Targeting option offered.
`free_trial`	No
`live_status`	No	Current aggregated status.
`support_24_7`	No	Claims 24/7 support.
`certification`	No	Certification or membership (ISO 27001, SOC 2, EWDCI, IWF).
`min_countries`	No	Minimum number of countries (for the given type when type is set).
`pricing_model`	No
`listing_status`	No	Default "active"; "any" includes pre-launch, defunct, suspended and unverifiable listings.
`unlimited_bandwidth`	No	A product whose traffic is (true) or is not (false) unmetered.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 4, 2026

TDQS

A3.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds substantial behavioral context: the return envelope, default listing_status active, default limit 20 and max 200, product-filter conjunction semantics, unknown-value behavior, and warnings. This is exactly the kind of operational detail annotations cannot provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description front-loads purpose and return shape, then defaults and filter constraints. It is dense but every sentence carries operational meaning for a 24-parameter tool; structure could be slightly easier to scan, but there is little waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description supplies the return envelope and warns about applied filters and warnings. Combined with 88% schema coverage and read-only annotations, it gives an agent enough information to call and interpret the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is high at 88%, so the baseline is 3, but the description adds cross-parameter meaning: max_price is in the matching product's price_unit and should be combined with type and pricing_model, and product filters must all hold for the same product. Those constraints are not fully captured by individual parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Filter, sort and page the provider database', and even names the equivalent API endpoint. It does not explicitly distinguish itself from siblings such as list_providers or get_provider, so it falls short of a full 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling tool is named as an alternative. Usage is only implied by 'filter, sort and page' and the API-equivalence note, leaving an agent without routing help versus list_providers or get_provider.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Working Proxy Sites tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?