web-api-mcp server
io.oxylabs/web-api-mcpoxylabs.iostreamable-httpv0.3.2Scanned
Search the live web, look up companies and read any page through the Oxylabs Web API.
7 tools: 2 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 7
- Can send data out · 3
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the web-api-mcp server can do
The web-api-mcp server is published by oxylabs.io, a domain the MCP Registry verified. It has 7 tools. It can create or change data (2 tools: check_requests and run_scraper), but cannot delete data. 5 tools only read.
7 tools bring in text other people can write (search, search_companies, scrape and 4 more); 3 tools can send data out of your system (scrape, list_scrapers and run_scraper).
The fixed checks matched 3 findings (annotation-conflict and long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 0.3.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 2Claude Code: ask
check_requestsCollect requests the API is running in the background.Reads text others write1 finding
Why it is in this group
- The name "check_requests" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "check_requests" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "check_requests" says "request": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- openWorldHint: true
- readOnlyHint: true
- title: Collect queued requests
run_scraperRun a dedicated scrape endpoint with its own parameters.Reads text others writeCan send data out2 findings
Why it is in this group
- The name "run_scraper" says "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "scrape": it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.
Findings
- Info
The description is 2,337 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "......` endpoint, or one `list_scrapers` lists only in async form, is always queued."
- Warn
The server marks "run_scraper" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "run_scraper" says "run": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- openWorldHint: true
- readOnlyHint: true
- title: Run a dedicated scraper
Only reads 5Show 5 read-only tools
list_scrapersList the scrape endpoints this API implements, or describe one of them.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "list_scrapers" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "scrape": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.endpoint), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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`.
Annotations the server declares
- openWorldHint: true
- readOnlyHint: true
- title: List scrape endpoints
read_resultRead a long page of a result in parts, from where its reply cut it short.Reads text others writeNo findings
Why it is in this group
- The name "read_result" says "read": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "read" and "reply": it reads comments, which other people can write.
Description, as the server wrote it 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`.
Annotations the server declares
- openWorldHint: true
- readOnlyHint: true
- title: Read a long result in parts
scrapeFetch and read web pages, including JavaScript-heavy and bot-protected ones.Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "fetch": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "scrape" says "scrape": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "fetch" and "web": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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.
Annotations the server declares
- openWorldHint: true
- readOnlyHint: true
- title: Read a page
searchSearch the live web and return ranked organic results.Reads text others writeNo findings
Why it is in this group
- The name "search" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "search" and "web": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- openWorldHint: true
- readOnlyHint: true
- title: Web search
search_companiesSearch for companies and return their profiles, best match first.Reads text others writeNo findings
Why it is in this group
- The name "search_companies" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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`.
Annotations the server declares
- openWorldHint: true
- readOnlyHint: true
- title: Company search
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write7
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:20 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.oxylabs.io/web-api-mcp: tools/list returned 7 tools to an anonymous client, including check_requests (write), run_scraper (write)
Findings
Matches of fixed checks, with the text they matched.
- Warncheck_requests
The server marks "check_requests" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "check_requests" says "request": a word for a change.
- Warnrun_scraper
The server marks "run_scraper" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "run_scraper" says "run": a word for a change.
- Inforun_scraper
The description is 2,337 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "......` endpoint, or one `list_scrapers` lists only in async form, is always queued."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.3.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http web-api https://mcp.oxylabs.io/web-api-mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http web-api https://mcp.oxylabs.io/web-api-mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__web-api__search",
"mcp__web-api__search_companies",
"mcp__web-api__read_result"
],
"ask": [
"mcp__web-api__scrape",
"mcp__web-api__check_requests",
"mcp__web-api__list_scrapers",
"mcp__web-api__run_scraper"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as web-api. Review it before you use it.
Capability tags behind 7 rules
- mcp__web-api__search untrusted-input
- mcp__web-api__search_companies untrusted-input
- mcp__web-api__scrape untrusted-input, outbound
- mcp__web-api__check_requests untrusted-input
- mcp__web-api__read_result untrusted-input
- mcp__web-api__list_scrapers untrusted-input, outbound
- mcp__web-api__run_scraper untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.oxylabs/web-api-mcp/verify?hash=9f587d07a1f6c33915a911ad1bd71fb2e6bdb34f7963c6efc8c4961a3f567bab" | jq -e '.changed == false'Pinned hash 9f587d07a1f6, from Nov 20, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.oxylabs/web-api-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.oxylabs/web-api-mcp)Source: MCP Registry · repository. Synced Nov 20, 2026, 13:18 UTC.
web-api-mcp server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the web-api-mcp server safe?
- No scan can promise that. What its definitions show: 7 tools, 2 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the web-api-mcp server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the web-api-mcp server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the web-api-mcp server have?
- 7 tools: 2 write, 5 read. check_requests, run_scraper, search, search_companies, scrape, read_result and list_scrapers.
Does the web-api-mcp server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the web-api-mcp server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): scrape, list_scrapers and run_scraper.
Has the web-api-mcp server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.