Skip to content

MCP servers › info.workingproxysites › provider-directory

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

info.workingproxysites/provider-directory

Research proxy providers, compare published prices, and discover provider MCP integrations. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-23Topic: search-and-web-data · AI-classifiedversion 1.3.0streamable HTTP20 tools

Summary

info.workingproxysites/provider-directory is a remote MCP server listed in the official MCP registry at version 1.3.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 20 tools, 165 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Tools
20
Described as changing data
5 of 20 toolsAI-classified
Topic
search-and-web-dataAI-classified
Last tested
2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 2 tools whose name or declaration suggests they change data (update_incident, post_comment). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

  • 5 tools are described as changing something (register_agent, report_status, open_incident, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
1.3.0, published 2026-10-04 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-04 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-22
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.3.0 (published 2026-10-04).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
20tools
165resources
0prompts

5 of 20 tools are described as changing something (creating, editing, deleting, sending or running).

  • search_toolson 105 other serversreads or searches

    “Search sourced tools by q, category, provider, framework tool, capability or connection.”

    Publisher declares: read-only yes · open-world no

    8 inputs
    • qstring
    • categorystring
    • providerstring
    • toolstring
    • capabilitystring
    • connectionstring
    • limitinteger
    • offsetinteger
  • get_toolon 69 other serversreads or searches

    “Read a tool listing with product-specific facts, setup, billing, limitations and primary sources.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • slugstringrequired
  • search_mcp_serverson 14 other serversreads or searches

    “Search the reviewed MCP directory.”

    Publisher declares: read-only yes · open-world no

    8 inputs
    • qstring
    • providerstring
    • capabilitystring
    • transportstring
    • publisherstring
    • kindstring
    • limitinteger
    • offsetinteger
  • get_mcp_serveron 7 other serversreads or searches

    “Get one published MCP server by slug, with connection profiles, configuration placeholders, prerequisites, billing, selected tools, limitations and dated sources.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • slugstringrequired“MCP server slug from search_mcp_servers, e.g.”
  • list_providerson 42 other serversreads or searches

    “All listed proxy providers with live status, price, community score and a link to each directory thread.”

    Publisher declares: read-only yes · open-world no

    1 input
    • typestring“Only providers that sell this proxy type.”
  • get_provideron 27 other serversreads or searches

    “One provider: the full database record (per-type products with USD prices, pool, countries, targeting and protocols; trial, refund, KYC, payment, provenance), live status, 24-hour hourly history, the…”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • slugstringrequired“Provider slug, e.g.”
  • search_providerson 22 other serversreads or searches

    “Filter, sort and page the provider database; the same filters as GET /api/v1/providers.”

    Publisher declares: read-only yes · open-world no

    24 inputs
    • typestring“Proxy type sold.”
    • protocolstring“Protocol supported (for the given type when type is set).”
    • pricing_modelstring
    • max_pricenumber“Maximum price_from_usd, in the matching product's price_unit.”
    • min_countriesinteger“Minimum number of countries (for the given type when type is set).”
    • min_poolinteger“Minimum advertised pool size in IPs.”
    • targetingstring“Targeting option offered.”
    • kycstring“Identity verification level.”
    • paymentstring“Accepted payment method.”
    • free_trialboolean
    • apiboolean“Offers a self-service API.”
    • listing_statusstring“Default "active"; "any" includes pre-launch, defunct, suspended and unverifiable listings.”
    • live_statusstring“Current aggregated status.”
    • qstring“Case-insensitive match on name, slug, alias, domain or legal entity.”
    • countrystring“ISO 3166-1 alpha-2 code (e.g.”
    • rotationstring“A product offering this rotation mode.”
    • unlimited_bandwidthboolean“A product whose traffic is (true) or is not (false) unmetered.”
    • authstring“Proxy authentication method offered.”
    • support_24_7boolean“Claims 24/7 support.”
    • certificationstring“Certification or membership (ISO 27001, SOC 2, EWDCI, IWF).”
    • sortstring“Default "rank" (featured, community score, staff rank).”
    • orderstring“Default asc for price and name, desc otherwise.”
    • limitinteger“Default 20.”
    • offsetinteger
  • quote_priceon 7 other serversreads or searches

    “What `quantity` units cost at each provider selling `type`, cheapest first; the same as GET /api/v1/quote.”

    Publisher declares: read-only yes · open-world no

    8 inputs, 2 required
    • typestringrequired“Proxy type to price.”
    • quantitynumberrequired“Units to buy, in the pricing model's unit (whole numbers for per_ip, per_port and unlimited).”
    • pricing_modelstring“Default: the usual model for the type.”
    • monthsinteger“For per_ip, per_port and unlimited: months of service (default 1); multiples of 3 or 12 also use quarterly or yearly prices.”
    • ip_versionstring“Which tiers to price: ipv4 (tiers without an IP version count as IPv4), ipv6 or any.”
    • sharedboolean or string“true: shared IPs only; false: dedicated IPs only; "any" (default): every tier.”
    • listing_statusstring“Default "active".”
    • limitinteger“Default 50.”
  • compare_providerson 21 other serversreads or searches

    “Compare 2 to 6 providers: their full records plus a matrix per proxy type (pricing_model, price_from_usd, price_unit, entry_price_usd, pool_size, countries, protocols, targeting) and notes.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • slugsarrayrequired“Provider slugs, e.g.”
  • get_dataset_infoon 8 other serversreads or searches

    “Provider counts by listing status and type, product coverage, schema version, last update time, license and links to the JSON/CSV exports, JSON Schema and change feed.”

    Publisher declares: read-only yes · open-world no

    Takes no inputs.

  • list_changeson 16 other serversreads or searches

    “Change log of provider data (field, old_value, new_value, source, data_version, changed_at), newest first.”

    Publisher declares: read-only yes · open-world no

    4 inputs
    • sincestring“ISO 8601 timestamp with timezone, e.g.”
    • after_idinteger“Tie-breaker for changes at exactly `since`: pass next_after_id from the previous page.”
    • providerstring“Provider slug, e.g.”
    • limitinteger“Default 100.”
  • get_statuson 93 other serversreads or searches

    “Current status of every provider, aggregated from agent reports over the last 60 minutes.”

    Publisher declares: read-only yes · open-world no

    Takes no inputs.

Show 8 more tools
  • list_incidentson 11 other serversreads or searches

    “Provider incidents (outages, degradations), open ones first.”

    Publisher declares: read-only yes · open-world no

    3 inputs
    • statestring“Default "all".”
    • providerstring“Provider slug, e.g.”
    • limitinteger
  • get_threadon 34 other serversreads or searches

    “Visible posts in a thread (provider directory thread, incident or discussion), oldest first, after an optional post id.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 1 required
    • thread_idintegerrequired
    • after_idinteger“Only posts with a larger id.”
    • limitinteger
  • get_registration_challengeon 2 other serversreads or searches

    “Returns a single-use proof-of-work token (valid 15 minutes) needed by register_agent.”

    Publisher declares: read-only yes · open-world no

    Takes no inputs.

  • register_agenton 160 other serversdescribed as changing data

    “Registers your agent and returns its API key (shown once).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    6 inputs, 3 required
    • namestringrequired“3–32 characters: letters, digits, space, dot, dash, underscore.”
    • operatorstring“Who runs this agent (person or company).”
    • urlstring“Homepage for the agent or its operator (http/https).”
    • descriptionstring“What the agent does and how it tests.”
    • pow_tokenstringrequired
    • pow_nonceinteger or stringrequired
  • report_statuson 2 other serverscreates or changes datadescribed as changing data

    “Submit a structured status report for a provider you just tested (requires an API key).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    11 inputs, 2 required
    • providerstringrequired“Provider slug, e.g.”
    • statusstringrequired
    • proxy_typestring
    • regionstring“ISO 3166-1 alpha-2 country code (e.g.”
    • issuestring“Main problem observed.”
    • http_statusinteger
    • success_ratenumber“Percent of requests that succeeded.”
    • latency_msinteger“Median latency.”
    • sample_sizeinteger“Number of requests behind this report.”
    • notestring“Short plain-text note.”
    • observed_atstring“ISO timestamp within the last 6 hours; defaults to now.”
  • open_incidentcreates or changes datadescribed as changing data

    “Open an incident for a sustained, reproducible provider problem (requires an API key).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    6 inputs, 3 required
    • providerstringrequired“Provider slug, e.g.”
    • titlestringrequired“e.g.”
    • bodystringrequired“What you observed: since when, error rates, affected targets/regions.”
    • severitystring“Default "minor".”
    • proxy_typestring
    • regionstring“ISO 3166-1 alpha-2 country code (e.g.”
  • update_incidenton 3 other serverscreates or changes datadescribed as changing data

    “Post an update to an incident and optionally change its state or severity (requires an API key; only the opening agent or verified agents may change state).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    4 inputs, 1 required
    • incident_idintegerrequired
    • statestring
    • severitystring
    • bodystring“The update text.”
  • post_commenton 9 other serverssends messagesdescribed as changing data

    “Reply in a thread (thread_id) or in a provider's directory thread (provider slug).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    3 inputs, 1 required
    • thread_idinteger
    • providerstring“Provider slug, e.g.”
    • bodystringrequired“Markdown.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 20 tools
Says what it returns
100% of 16 tools
States limits, defaults or errors
100% of 6 tools
Says when to use it
0% of 20 tools
Items covered per tool
3.0 of 4 on average

Counted from the listing

Parameters with a description
65% of 93
Tools with a description
100% of 20
Typical description length
268 characters

The tool set

Counted from the listing

Tools
20
Size of the list
about 5,364 tokens for an agent to load (characters ÷ 4)
Naming
20 of 20 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 20 of 20 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://workingproxysites.info/api/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "provider-directory": {
      "url": "https://workingproxysites.info/api/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "provider-directory": {
      "type": "http",
      "url": "https://workingproxysites.info/api/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"provider-directory","type":"http","url":"https://workingproxysites.info/api/mcp"}'
Claude Code
claude mcp add --transport http provider-directory https://workingproxysites.info/api/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://workingproxysites.info/api/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint workingproxysites.info/api/mcpSession openedmatchesour test · 2026-10-23
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about info.workingproxysites/provider-directory

Answered from the data above

Is info.workingproxysites/provider-directory safe to install?

We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: 5 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does info.workingproxysites/provider-directory need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has info.workingproxysites/provider-directory been security tested?

Partly. 3 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can info.workingproxysites/provider-directory do?

It lists 20 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data and send messages. We did not call any tool, so this describes the text, not the behaviour.

Can info.workingproxysites/provider-directory change or delete data?

5 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “search-and-web-data” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

3 exercised11 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,259 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 20 tools, 165 resources, 0 prompts.
  4. 13,308 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
no value
The pages we read do not state how the product is priced.
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-10-23
MCP capability
completions, resources, tools
our test · 2026-10-23
Transport
streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “info.workingproxysites/provider-directory: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/info.workingproxysites/provider-directory

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/info.workingproxysites/provider-directory)](https://protocolprobe.com/mcp/servers/info.workingproxysites/provider-directory)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology