workingproxysites.

MCP directory

Web Search MCP Servers: Tools, Connections & Account Requirements

Compare documented web-search MCP integrations by publisher, transport, credentials, available tools and commercial requirements.

Select an MCP integration that documents web-search capability and the required connection/account setup.

  • Does the server search for URLs or fetch a URL you already know?
  • Which search tool and account product does the integration document?
  • Can your client use the listed hosted connection or local runtime?
12 documented listings

This collection covers our reviewed proxy and web-data catalog. It is not an exhaustive market survey or a performance ranking.

Category reviewed . Review due .

Compare documented requirements

12 of 12 listings
Clear filters

Swipe or scroll horizontally to compare requirements. Scroll back to the first column to see listing names.

MCP connections, tool scope and account requirements · alphabetical
MCP serverConnection & credentialsDocumented toolsBilling & restrictionsEvidence
Apify MCPApify · official publisher

Find Apify Actors, inspect their inputs and pricing, run a selected Actor, and retrieve its dataset through the official MCP server.

Details & setup →Provider discussionSourced JSON record
Streamable HTTP · hosted

Bearer Apify API token; the hosted server also supports OAuth sign-in.[1][4]

Local stdio · local

Apify API token in the APIFY_TOKEN environment variable.[1][2][5]

  • search-actors

    Find Actors in Apify Store.[2]

  • fetch-actor-details

    Read an Actor input schema, description and pricing.[2]

  • call-actor

    Start the selected Actor with its documented input.[2]

  • get-actor-run

    Read a run status and its associated storage identifiers.[2]

  • get-dataset-items

    Read dataset rows with pagination and filtering.[2]

The configured token uses the Apify account balance. Actor pricing can be per event or platform usage; compute, proxies, storage and data transfer may contribute. Inspect the selected Actor pricing before execution.

Required product: Apify Actors and platform usage

Requirements & limitations
  • Actor availability and behavior depend on the chosen Actor and server configuration.
  • Local stdio lacks hosted output-schema inference.
  • These setup details were checked against documentation; no authenticated run was performed.
Documentation checkedReview due
5 source references
Bright Data MCPBright Data · official publisher

Search the public web, retrieve page content and use optional browser tools through Bright Data’s hosted or local MCP integration.

Details & setup →Provider discussionSourced JSON record
Streamable HTTP · hosted

Bright Data API token in the token query parameter.[2][4][6]

Local stdio · local

API_TOKEN environment variable.[4][5][6]

  • search_engine

    Retrieve results from a supported search engine.[3]

  • scrape_as_markdown

    Read one page as Markdown.[3]

  • scraping_browser_navigate

    Navigate a remote browser session; optional browser tools must be enabled.[4]

API usage draws from the account’s allowances; additional usage and optional tools follow the applicable product terms. Free server software does not make all API usage free.

Required product: Bright Data Web Unlocker API; additional products may be used by optional tools.

Requirements & limitations
  • The default mode and optional Pro or tool groups expose different tools. Browser automation needs the relevant group or Pro mode.
  • The remote template contains a token placeholder in its URL; replace it only in your own client configuration.
  • The reviewed tool documentation does not establish proxy purchasing or proxy account management.
Documentation checkedReview due
6 source references
Decodo MCPDecodo · official publisher

Retrieve pages, search results and supported structured targets through Decodo’s Web Scraping API.

Details & setup →Provider discussionSourced JSON record
Streamable HTTP · hosted

Authorization: Basic followed by the Web Scraping API token.[1][2][4]

  • scrape_as_markdown

    Return a requested page as Markdown.[1]

  • google_search

    Retrieve parsed Google results.[1]

  • amazon_product

    Retrieve a supported Amazon product page.[1]

Scraping usage is billed under the account plan; request features such as rendering and proxy pool affect consumption.

Required product: Decodo Web Scraping API.

Requirements & limitations
  • The toolsets parameter restricts which tools are exposed; all tools are registered when it is omitted.
  • JavaScript rendering is documented, but this listing does not infer an interactive browser-control capability.
  • The reviewed tool documentation does not establish proxy purchasing or proxy account management.
Documentation checkedReview due
4 source references
Evomi MCPEvomi · official publisher

Inspect Evomi proxy products, targeting and usage, rotate sessions, and run scraping jobs through a local Python MCP server.

Details & setup →Provider discussionSourced JSON record
Local stdio · local

EVOMI_PUBLIC_API_KEY environment variable; a separate scraper key can optionally override automatic lookup.[1][2][3][4][6]

  • list_proxy_products

    Inspect account products, gateways, ports and balances.[1]

  • list_proxy_targeting_options

    Find supported locations and network targeting values.[1]

  • get_proxy_usage

    Read recent bandwidth consumption.[2]

  • rotate_proxy_session

    Change the exit IP of a sticky session.[2]

  • scrape_url

    Retrieve a page with scraping options, including documented browser mode.[1]

  • search_domains

    Find domains from a search query.[2]

Scraping consumes credits according to mode and options. Proxy traffic uses the applicable product allowance. The software license does not include API usage.

Required product: Evomi Public API access plus the proxy or Scraper API product used by the tool.

Requirements & limitations
  • Credential tools can return live proxy passwords to the connected model and its client logs. EVOMI_HIDE_PROXY_PASSWORDS=1 masks or disables those outputs.
  • rotate_proxy_session changes a live session. Account and scraping tools are not all read-only.
  • The EVOMI_ENABLE_SPENDING flag controls browser-profile ordering; ordinary scraping still consumes credits when that flag is absent.
  • The uvx template adapts the documented evomi-mcp command using Astral’s tool launcher. Package 1.3.1 was reviewed; the unpinned command can install a newer release.
Documentation checkedReview due
6 source references
Infatica Data Platform MCPInfatica · official publisher

Infatica’s hosted MCP connection for data collection runs, result exports, analyses and recurring schedules, authorized by a scoped Personal Access Token.

Details & setup →Provider discussionSourced JSON record
Streamable HTTP · hosted

Personal Access Token in the Authorization: Bearer header, with scopes for the intended tools.[1]

  • list_runs

    Read the account’s runs and apply documented filters.[1]

  • create_run

    Start a data collection run; requires runs:write.[1][2]

  • get_run

    Read a run and its item statuses.[1]

  • export_run

    Export collected results in a supported file format.[1]

  • compare_runs

    Create an analysis comparing collected runs; requires analyses:write.[1]

  • create_schedule

    Create a recurring run schedule; requires schedules:write.[1]

  • get_usage_summary

    Read the account’s usage summary with daily detail.[1]

Platform access is included with eligible Web Scraper Pro plans and uses the same request quota as the API. Check the current plan eligibility and account quota before creating runs.

Required product: Infatica Data Platform / Web Scraper Pro

Requirements & limitations
  • An Infatica account with Data Platform access and a Personal Access Token is required.
  • Tool access depends on token scopes; schedule listing also requires schedules:write.
  • Write tools can create billable runs or change schedules. Cancellation and deletion tools also exist in the upstream catalog.
  • Documentation confirmed; no authenticated connection test was performed.
Documentation checkedReview due
3 source references
Nimble MCPNimble · official publisher

Search for sources, map a website and extract selected URLs through Nimble hosted MCP tools.

Details & setup →Provider discussionSourced JSON record
Streamable HTTP · hosted

Send a Nimble API key as a Bearer credential. Nimble also documents OAuth through supported plugin installation.[1]

  • nimble_search

    Find web sources with configurable search behavior.[1][2]

  • nimble_extract

    Retrieve content from a known URL.[1][2]

  • nimble_map

    Discover website URLs using links and sitemaps.[1][2]

The published API model charges for successful requests, with different rates by product. Search depth and requested content can affect search cost. Managed Data Services plans and research-agent task pricing are separate considerations.

Required product: Nimble API usage

Requirements & limitations
  • Available parameters should be checked in the client-discovered tool schema.
  • Search, extraction and research-agent work have different billing bases.
  • The configuration and tool names are documentation-confirmed; no authenticated connection was tested.
Documentation checkedReview due
5 source references
Novada MCPNovada · official publisher

Search, extract pages, use browser tools and configure proxy connections through Novada’s hosted endpoint or local npm package.

Details & setup →Provider discussionSourced JSON record
Streamable HTTP · hosted

Authorization: Bearer YOUR_NOVADA_API_KEY header.[3][5]

Local stdio · local

NOVADA_API_KEY environment variable.[3][5][6]

  • novada_setup

    Check API-key configuration and account readiness.[3]

  • novada_discover

    Inspect the tools available on this connection.[2]

  • novada_search

    Find pages using a search query and supported filters.[2]

  • novada_extract

    Retrieve content from selected URLs.[2]

  • novada_browser

    Perform documented page interactions.[2]

  • novada_proxy

    Produce proxy connection settings for an HTTP client.[2]

Scraping products draw from shared credits, with consumption depending on the product and request. Proxy plans and other product quotas can impose separate limits. Check both balance and the selected product.

Required product: Novada account with access to the scraping, browser or proxy product selected by the tool.

Requirements & limitations
  • Hosted and local connections expose different tools. Call novada_discover on the chosen connection instead of relying on a fixed tool count.
  • Persistent browser flows and some account-changing operations require the local server. Available operations must be checked on that profile.
  • Proxy connection output is used by your own HTTP client; it does not make arbitrary HTTP traffic flow through the MCP protocol.
  • The example uses an Authorization header for clients supporting remote headers. Query-string credential alternatives in the provider guide should not be shared.
Documentation checkedReview due
6 source references
Oxylabs MCPOxylabs · official publisher

Connect an agent to Oxylabs scraping and AI Studio tools, with separate credentials for each product.

Details & setup →Provider discussionSourced JSON record
Streamable HTTP · hosted

X-Oxylabs-Username and X-Oxylabs-Password request headers.[1][3]

  • universal_scraper

    Retrieve page content with optional rendering.[1]

  • google_search_scraper

    Retrieve Google results.[1]

  • ai_browser_agent

    Run a prompted browser task with AI Studio credentials.[1]

Web Scraper API plans bill by successful results, with target and rendering affecting consumption. AI Studio has separate product usage terms.

Required product: Oxylabs Web Scraper API for the included setup; AI Studio requires its own key.

Requirements & limitations
  • The official repository was archived on 2026-09-16. Its documented hosted endpoint has not been connection-tested by WPS; ongoing maintenance is unconfirmed.
  • This setup enables Web Scraper API requests. AI Studio tools require an additional X-Oxylabs-AI-Studio-Api-Key header.
  • Hosted tools may be listed without their required credentials; those calls fail until the correct product credentials are supplied.
  • The reviewed tool documentation does not establish proxy purchasing or proxy account management.
Documentation checkedReview due
3 source references
ScraperAPI MCPScraperAPI · official publisher

Connect to hosted ScraperAPI tools for URL scraping, parsed Google results and structured shopping data.

Details & setup →Provider discussionSourced JSON record
Streamable HTTP · hosted

Send the ScraperAPI API key as a Bearer credential.[1][5]

  • scrape

    Fetch a URL with optional rendering and output formatting.[2]

  • google_search

    Return parsed Google Search results.[2][1]

  • google_shopping

    Return parsed Google Shopping product results.[2][1]

Successful requests consume credits from the account plan. Target sites, structured endpoints and options such as rendering or premium routing affect request cost. Plans also have concurrency limits.

Required product: ScraperAPI API credits

Requirements & limitations
  • Rendering and premium routing can change credit use.
  • Structured endpoint inputs differ from the generic scrape tool.
  • Documentation was checked; no account-backed calls were made.
Documentation checkedReview due
5 source references
ScrapingBee MCPScrapingBee · official publisher

Use ScrapingBee’s hosted MCP endpoint to search the web and retrieve page content with scraper API options.

Details & setup →Provider discussionSourced JSON record
Streamable HTTP · hosted

Authorization: Bearer followed by a ScrapingBee API key.[1][4]

  • fast_search

    Retrieve structured web search results.[2]

  • get_page_text

    Retrieve a page as Markdown or text.[2]

  • extract_page_data

    Extract fields using supported selectors or extraction options.[2]

Calls consume API credits according to the chosen features and proxy options; account plan limits apply.

Required product: ScrapingBee API account.

Requirements & limitations
  • The hosted endpoint needs a Bearer API key header. The older api_key URL parameter is deprecated.
  • Requests can consume different numbers of credits when rendering or proxy options change.
  • The reviewed tool documentation does not establish proxy purchasing or proxy account management.
Documentation checkedReview due
4 source references
Singapore Mobile Proxy MCPSingapore Mobile Proxy · official publisher

Fetch pages, check Singapore-localized Google results and inspect or rotate the provider’s mobile proxy exit through a hosted MCP endpoint.

Details & setup →Provider discussionSourced JSON record
Streamable HTTP · hosted

A Singapore Mobile Proxy MCP key in the x-api-key header.[1][2][5]

  • my_proxy_status

    Read the current exit, carrier and remaining quota.[1]

  • fetch_url

    Fetch a URL as Markdown, text or HTML through the provider’s Singapore proxy.[1]

  • search_google

    Retrieve Singapore-localized Google organic results.[1]

  • rotate_ip

    Request a new Singapore mobile exit IP.[1]

MCP onboarding offers a limited trial; continued use requires the provider’s paid access. Confirm remaining quota and plan terms in the account.

Required product: Singapore Mobile Proxy MCP access and its proxy plan.

Requirements & limitations
  • This service specializes in Singapore; it is not a multi-country location selector.
  • The documented rotate_ip tool changes the proxy exit. Review that action before a workflow that relies on a stable session.
  • Carrier identity and connectivity were not independently tested.
  • The pricing page mixes bandwidth-labelled plans with unlimited wording. Confirm the applicable quota in the MCP account before relying on an allowance.
Documentation checkedReview due
5 source references
Thordata MCPThordata · official publisher

Connect to Thordata’s hosted SERP MCP service for engine discovery, search results and account usage history.

Details & setup →Provider discussionSourced JSON record
Streamable HTTP · hosted

Thordata SERP API token replaces YOUR_API_TOKEN in the endpoint path.[1][2][6]

  • list_engines

    List engines and their schema resources.[2]

  • search

    Request search results using an engine-specific parameter object.[2]

  • history

    Read SERP request history.[2]

  • statistics

    Read SERP usage statistics for a date interval.[2]

SERP plans provide response allowances. The billing guide charges successful HTTP 200 searches, including successful responses with few or no matching results; other status codes are not billed.

Required product: Thordata SERP API.

Requirements & limitations
  • This record covers the hosted SERP integration. The reviewed tools do not establish general page extraction, browser control or proxy-account management.
  • The documented connection places the API token in the URL path. Treat the completed URL as a credential and keep shared examples placeholder-only.
  • Engine-specific search parameters must follow the corresponding schema resource. A field accepted by one engine may not apply to another.
Documentation checkedReview due
6 source references

How to use this comparison

Compare the documented request interface, output and account product before checking price. A JSON response can contain raw HTML; it does not by itself establish structured extraction. A browser action in one request does not by itself establish a reusable browser session.

Each row keeps the publisher’s billing basis and restrictions alongside its sources. Unknown prices or limits remain unknown. These are documentation reviews; no live connection, purchase or comparative performance test is claimed.

Overdue records remain visible with a label. This collection leaves search indexing when its category review is overdue or fewer than 3 current, visible records qualify. Individual detail pages retain their own review policy.

The collection JSON link covers the whole category before filters. It returns summaries; use each listing’s Sourced JSON record link for full sources, connections, tools and billing.

Suggest a correction · Affiliate disclosure · Collection JSON summaries