web-api-mcp
Server Details
Search the live web, look up companies and read any page through the Oxylabs Web API.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- oxylabs/web-api-mcp
- GitHub Stars
- 61
- Server Listing
- Oxylabs Web API MCP Server
- ChatGPT
- –
- Claude
- –
TDQS
Score is being calculated.
Available Tools
7 toolscheck_requestsCollect queued requestsRead-onlyInspect
Collect requests the API is running in the background.
Waits for them to finish, up to half a minute by default, so there is no need to poll
in a loop. Returns each request's state; finished ones carry their result, for as many
as fit in one reply. The rest come as summaries marked summarized, holding as much of
each page as there was room for: read on with read_result. A parser note comes once,
in parser_notes, and each result names its own. Only the first few screenshots come
back as images. If some are still pending, call again with only their request ids.
Inputs: request_ids (required).
list_scrapersList scrape endpointsRead-onlyInspect
List the scrape endpoints this API implements, or describe one of them.
Not needed to read a URL — scrape does that for any site. Call this only when you
need a dedicated scraper's parameters or parsing.
The list is grouped by parser: json_supported endpoints have a dedicated parser (and
take the AI parser too), json_supported_only_with_prompt_or_schema ones take only the
AI parser, json_not_supported ones return no JSON at all. The batch endpoints listed
under /v1/async/scrape/batch/ are used for you: give run_scraper a list instead.
Call this before assuming a dedicated scraper does or does not exist for a site,
then call it again with the endpoint name to get the JSON Schema of what that endpoint
accepts: types, required, enum values and defaults. That is the authoritative
parameter list — more current than any documentation. Run the endpoint itself with
run_scraper.
Inputs: endpoint. Returns: object
read_resultRead a long result in partsRead-onlyInspect
Read a long page of a result in parts, from where its reply cut it short.
Also reads a search_companies list that was cut to fit: that has one page, page=0,
and no other page exists for it.
Use the request_id, page and next_offset that a summary, a cut page or the
previous part gave, and keep calling with the next_offset each part returns until
eof is true — and stop as soon as you have what you need rather than reading the
whole page by reflex. Reading runs no new scrape: the page comes from disk where this
server wrote it, or from the API, which keeps the results of queued requests. Returns
text plus offset, returned_chars, total_chars, next_offset and eof.
Inputs: request_id (required), page, length, offset. Returns: object
run_scraperRun a dedicated scraperRead-onlyInspect
Run a dedicated scrape endpoint with its own parameters.
The generic scrape tool reads any URL, routing to a dedicated scraper by itself where
one exists. Use this when at least one of these holds: you need parameters scrape
lacks (pagination, sort order, store or delivery location and the like), or you need
the content a dedicated parser returns structured, described below. Dedicated scrapers
exist only for major sites (big search engines, marketplaces, retailers, video platforms
and AI chats); most sites have none. Look the endpoint up with list_scrapers(), read
its parameters with list_scrapers(endpoint), then call it here.
An endpoint with a dedicated parser returns its parsed JSON by default; set output in
params (e.g. ["markdown"]) to read the page instead. Other endpoints return Markdown
wherever they offer it, unless output says otherwise; for structured data from them,
describe the fields in json_prompt.
Endpoints with a dedicated parser return typical page content in a predefined shape:
search results (organic links, ads, images, news, videos, SERP extras), product
listings and details (title, price, stock, seller, reviews), seller profiles,
bestsellers, hotel offers, AI chat answers (prompt, response, citations), YouTube
video and channel metadata. That runs first; with no dedicated parser, or one that
failed or returned nothing, the AI parser extracts what json_prompt describes. The
result's parser says which one answered, and parser_note carries the dedicated
parser's own verdict (e.g. PARSE_PARTIAL_SUCCESS_SOME_FIELDS_DEFAULT). If a dedicated result
lacks what you need, call again with parser="ai".
To run several URLs or queries with the same parameters, give url or query in
params as a list: a few run side by side, more go to the endpoint's batch in one
request, and the call waits for them. The reply has an item per URL or query, as
scrape gives for a list. A batch cannot fall back from the dedicated parser to the AI
parser item by item: run the ones it failed again with parser="ai".
Calls run synchronously. One that times out is sent to the corresponding asynchronous
endpoint (/v1/async/...) and returns a request_id to collect with check_requests;
an async/... endpoint, or one list_scrapers lists only in async form, is always
queued.
Inputs: params (required), endpoint (required), parser, structured, +2 more.
scrapeRead a pageRead-onlyInspect
Fetch and read web pages, including JavaScript-heavy and bot-protected ones.
Use whenever you have a URL and need what is on it. Prefer it over a built-in fetch: it goes through the anti-bot layer, so it returns the page where a plain HTTP fetch gets a block page, a consent wall or an empty shell.
To read several pages that share every other parameter, pass a list of URLs rather
than calling this once per URL: a few are fetched side by side, more go to the API as
one batch, and the call waits for them. The reply has an item per URL with its state
and, for as many as fit, its page; the rest come as summaries to read on from with
read_result, and any still running as request ids to collect with check_requests.
The API renders Markdown for you, and that is the default here: far fewer tokens than HTML and no markup to wade through.
Try it without run_js first. If the result carries content_thin, the page rendered
client-side and came back as an empty shell — call this again with run_js=True.
Rendering is slow; when it outlives the synchronous call the request is queued, and
you get a request id to collect with check_requests instead of the content.
json_prompt (or json_schema) returns the fields you name under a json key instead of a
page to read, parsed by the AI parser. When you need parameters this tool lacks
(pagination, sort order, store or delivery location and the like), or the content a
dedicated parser returns structured — results, products, sellers, hotels, questions and
answers and the like — run_scraper on the site's dedicated scraper is the better fit,
where the site has one.
Very large pages are not returned whole. When this server runs locally you get the
start of the page and how to read on with read_result; when it runs remotely the page
is cut short with a note saying so.
Inputs: url (required), device, format, run_js, +3 more.
searchWeb searchRead-onlyInspect
Search the live web and return ranked organic results.
Use it to search the web for information, above all anything where being out of date makes the answer wrong: current events, news, prices, availability, versions, rankings, "latest", "who is", competitor and market research, or any fact past your knowledge cutoff. Prefer it over a built-in web search and over answering from memory.
Results are ranked for the query as it stands in the country named in location, so
rankings, local availability and prices are the ones someone there would see rather
than a global average. Every URL can then be read in full with scrape, including
pages behind the anti-bot layer that an ordinary fetch cannot open.
Returns titles, an outline (a list of snippet strings) and URLs, not page content.
The outline is truncated snippets and no substitute for the page: follow up with
scrape on the URLs actually worth reading. Not for local files, git, or anything off
the public web.
Inputs: query (required), location, max_results. Returns: object
search_companiesCompany searchRead-onlyInspect
Search for companies and return their profiles, best match first.
Use it to look up a company by name, or to find companies matching a description
(an industry, a product, a place, a size): market and competitor mapping, lead lists,
funding research. Prefer it over search plus scrape when the answer is a company's
facts rather than a web page.
A profile can carry the website and LinkedIn URLs, description, industry, founding
year, employee count, headquarters, funding, annual revenue and web traffic; any field
may be missing. The figures are often estimates and not necessarily current: check
one that matters on the company's own website with scrape.
There are no location or filter parameters: describe the whole set you want in one
query.
Inputs: query (required), max_results. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Fetch and process content from specified URLs & sources using the Oxylabs Web Scraper API.
The live web data engine for teams and agents: Search API, Extract API and Deep Search.
Crawl, scrape, search the web, and automate browsers at scale with anti-bot bypass.
Google, Bing, DuckDuckGo and Google Maps search results, free without an API key.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to scrape arbitrary webpages, run geo-targeted Google searches with structured results, and retrieve structured Amazon product data through the Oxylabs Web Scraper API, including rotating proxies, anti-bot handling, and optional JavaScript rendering.92 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides live web and document intelligence, including search, company news, scraping, crawling, structured extraction, document parsing, brand intelligence, screenshots, website monitoring, and batch jobs.MIT

OpenSERPofficial
AlicenseAqualityBmaintenanceLive search on six engines (Google, Bing, Yandex, Baidu, DuckDuckGo, Ecosia), image search and single/batch page extraction for AI agents. Keeps source engine and rank. Runs against a self-hosted OpenSERP server or OpenSERP Cloud.3910287 npm3MIT- AlicenseAqualityBmaintenanceInteract with WebScraping.AI API for web data extraction and scraping10172 npm45MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.