io.oxylabs/oxylabs-mcp
REMOTE · MCP.OXYLABS.IO · 2 COMPONENTS
Fetch and process content from specified URLs & sources using the Oxylabs Web Scraper API.
Available components
Last scanned (13 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Web Scraping
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2975 tokens (~297/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Oct 26 0
- Server version: 0.10.0 → 0.10.2 functional
- 16 Oct 26 0
- Server version: 0.9.3 → 0.10.0 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 0
- Server version: 0.9.2 → 0.9.3 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Aug 26 0
- Server version: 3.4.6 → 0.9.2 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.oxylabs.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.oxylabs.io | CN=YE2,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5b1acb9a498921400b9150318cf3fc988bc |
| SANs: mcp.oxylabs.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.oxylabs.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| oxylabs.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.oxylabs.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.oxylabs.io/mcp | HTTPS enforced | 302 | https://mcp.oxylabs.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ai_browser_agent ~215
Run the browser agent and return the data in the specified format. This tool is useful if you need navigate around the website and do some actions. It allows navigating to any url, clicking on links, filling forms, scrolling, etc. Finally it returns the data in the specified format. Schema is required only if output_format is json, csv or toon. 'task_prompt' describes what browser agent should achieve
| Name | Type | Req | Description |
|---|---|---|---|
| geo_location | – | – | Two letter ISO country code to use for the browser proxy. |
| output_format | string | – | The output format. Markdown returns full text of the page including links. Toon(Token-Oriented Object Notation) returns data in Toon format, which is optimized for AI agents. If json, csv or toon, th… |
| schema | – | – | The schema to use for the scrape. Only required if output_format is json, csv or toon. |
| task_prompt | string | yes | What browser agent should do. |
| url | string | yes | The URL to start the browser agent navigation from. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ai_crawler ~307
Tool useful for crawling a website from starting url and returning data in a specified format. Schema is required only if output_format is json, csv or toon. 'render_javascript' is used to render javascript heavy websites. 'return_sources_limit' is used to limit the number of sources to return, for example if you expect results from single source, you can set it to 1.
| Name | Type | Req | Description |
|---|---|---|---|
| geo_location | – | – | Two letter ISO country code to use for the crawl proxy. |
| output_format | string | – | The format of the output. If json, csv or toon, the schema is required. Markdown returns full text of the page. CSV returns data in CSV format. Toon(Token-Oriented Object Notation) returns data in To… |
| render_javascript | boolean | – | Whether to render the HTML of the page using javascript. Much slower, therefore use it only for websites that require javascript to render the page. Unless user asks to use it, first try to crawl the… |
| return_sources_limit | integer | – | The maximum number of sources to return. |
| schema | – | – | The JSON schema to use for structured data extraction from the crawled pages. Only required if output_format is json, csv or toon. |
| url | string | yes | The URL from which crawling will be started. |
| user_prompt | string | yes | What information user wants to extract from the domain. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ai_map ~230
Tool useful for mapping website's URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_external_domains | boolean | – | Whether to include external domains URLs. |
| allow_subdomains | boolean | – | Whether to map subdomains URLs as well. |
| geo_location | – | – | Two letter ISO country code to use for the mapping proxy. |
| limit | integer | – | The maximum number of URLs to return. |
| max_crawl_depth | integer | – | The maximum depth of the crawl. |
| render_javascript | boolean | – | Whether to render the HTML of the page using javascript. Much slower, therefore use it only for websites that require javascript to render the page. Unless user asks to use it, first try to crawl the… |
| search_keywords | – | – | The keywords to use for URLs paths filtering. Keywords are matched as OR condition. Meaning, one keyword is enough to match the url path. |
| url | string | yes | The URL from which URLs mapping will be started. |
| user_prompt | – | – | What kind of URLs user wants to find. Can be used together with 'search_keywords'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ai_scraper ~238
Scrape the contents of the web page and return the data in the specified format. Schema is required only if output_format is json or csv. 'render_javascript' is used to render javascript heavy websites.
| Name | Type | Req | Description |
|---|---|---|---|
| geo_location | – | – | Two letter ISO country code to use for the scrape proxy. |
| output_format | string | – | The format of the output. If json, csv or toon, the schema is required. Markdown returns full text of the page. CSV returns data in CSV format, tabular like data. Toon(Token-Oriented Object Notation)… |
| render_javascript | boolean | – | Whether to render the HTML of the page using javascript. Much slower, therefore use it only for websites that require javascript to render the page.Unless user asks to use it, first try to scrape the… |
| schema | – | – | The JSON schema to use for structured data extraction from the scraped page. Only required if output_format is json, csv or toon. |
| url | string | yes | The URL to scrape |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ai_search ~194
Search the web based on a provided query. 'return_content' is used to return markdown content for each search result. If 'return_content' is set to True, you don't need to use ai_scraper to get the content of the search results urls, because it is already included in the search results. if 'return_content' is set to True, prefer lower 'limit' to reduce payload size.
| Name | Type | Req | Description |
|---|---|---|---|
| geo_location | – | – | Two letter ISO country code to use for the search proxy. |
| limit | integer | – | Maximum number of results to return. |
| query | string | yes | The query to search for. |
| render_javascript | boolean | – | Whether to render the HTML of the page using javascript. Much slower, therefore use it only if user asks to use it.First try to search with setting it to False. |
| return_content | boolean | – | Whether to return markdown content of the search results. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
amazon_product_scraper ~481
Scrape Amazon products. Supports content parsing, different user agent types, domain, geolocation, locale parameters and different output formats. Supports Amazon specific parameters such as currency and getting more accurate pricing data with auto select variant.
| Name | Type | Req | Description |
|---|---|---|---|
| autoselect_variant | boolean | – | To get accurate pricing/buybox data, set this parameter to true. |
| currency | – | – | Currency that will be used to display the prices. |
| domain | – | – | Domain localization for Google. Use country top level domains. For example: - 'co.uk' for United Kingdom - 'us' for United States - 'fr' f… |
| geo_location | – | – | The geographical location that the result should be adapted for. Use ISO-3166 country codes. Examples: - 'California, United States' - 'Mexico'… |
| locale | – | – | Set 'Accept-Language' header value which changes your Google search page web interface language. Examples: - 'en-US' for English, United States - 'de-AT' for… |
| output_format | – | – | The format of the output. Works only when parse parameter is false. - links - Most efficient when the goal is navigation or finding specific URLs. Use this first when you need to… |
| parse | boolean | – | Should result be parsed. If the result is not parsed, the output_format parameter is applied. |
| query | string | yes | Keyword to search for. |
| render | – | – | Whether a headless browser should be used to render the page. For example: - 'html' when browser is required to render the page. |
| user_agent_type | – | – | Device type and browser that will be used to determine User-Agent header value. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
amazon_search_scraper ~509
Scrape Amazon search results. Supports content parsing, different user agent types, pagination, domain, geolocation, locale parameters and different output formats. Supports Amazon specific parameters such as category id, merchant id, currency.
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | – | – | Search for items in a particular browse node (product category). |
| currency | – | – | Currency that will be used to display the prices. |
| domain | – | – | Domain localization for Google. Use country top level domains. For example: - 'co.uk' for United Kingdom - 'us' for United States - 'fr' f… |
| geo_location | – | – | The geographical location that the result should be adapted for. Use ISO-3166 country codes. Examples: - 'California, United States' - 'Mexico'… |
| locale | – | – | Set 'Accept-Language' header value which changes your Google search page web interface language. Examples: - 'en-US' for English, United States - 'de-AT' for… |
| merchant_id | – | – | Search for items sold by a particular seller. |
| output_format | – | – | The format of the output. Works only when parse parameter is false. - links - Most efficient when the goal is navigation or finding specific URLs. Use this first when you need to… |
| pages | integer | – | Number of pages to retrieve. |
| parse | boolean | – | Should result be parsed. If the result is not parsed, the output_format parameter is applied. |
| query | string | yes | Keyword to search for. |
| render | – | – | Whether a headless browser should be used to render the page. For example: - 'html' when browser is required to render the page. |
| start_page | integer | – | Starting page number. |
| user_agent_type | – | – | Device type and browser that will be used to determine User-Agent header value. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
generate_schema ~33
Generate a json schema in openapi format.
| Name | Type | Req | Description |
|---|---|---|---|
| app_name | string | yes | – |
| user_prompt | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
google_search_scraper ~489
Scrape Google Search results. Supports content parsing, different user agent types, pagination, domain, geolocation, locale parameters and different output formats.
| Name | Type | Req | Description |
|---|---|---|---|
| ad_mode | boolean | – | If true will use the Google Ads source optimized for the paid ads. |
| domain | – | – | Domain localization for Google. Use country top level domains. For example: - 'co.uk' for United Kingdom - 'us' for United States - 'fr' f… |
| geo_location | – | – | The geographical location that the result should be adapted for. Use ISO-3166 country codes. Examples: - 'California, United States' - 'Mexico'… |
| limit | integer | – | Number of results to retrieve in each page. |
| locale | – | – | Set 'Accept-Language' header value which changes your Google search page web interface language. Examples: - 'en-US' for English, United States - 'de-AT' for… |
| output_format | – | – | The format of the output. Works only when parse parameter is false. - links - Most efficient when the goal is navigation or finding specific URLs. Use this first when you need to… |
| pages | integer | – | Number of pages to retrieve. |
| parse | boolean | – | Should result be parsed. If the result is not parsed, the output_format parameter is applied. |
| query | string | yes | URL-encoded keyword to search for. |
| render | – | – | Whether a headless browser should be used to render the page. For example: - 'html' when browser is required to render the page. |
| start_page | integer | – | Starting page number. |
| user_agent_type | – | – | Device type and browser that will be used to determine User-Agent header value. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
universal_scraper ~279
Get a content of any webpage. Supports browser rendering, parsing of certain webpages and different output formats.
| Name | Type | Req | Description |
|---|---|---|---|
| geo_location | – | – | The geographical location that the result should be adapted for. Use ISO-3166 country codes. Examples: - 'California, United States' - 'Mexico'… |
| output_format | – | – | The format of the output. Works only when parse parameter is false. - links - Most efficient when the goal is navigation or finding specific URLs. Use this first when you need to… |
| render | – | – | Whether a headless browser should be used to render the page. For example: - 'html' when browser is required to render the page. |
| url | string | yes | Website url to scrape. |
| user_agent_type | – | – | Device type and browser that will be used to determine User-Agent header value. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.oxylabs/oxylabs-mcp server?
io.oxylabs/oxylabs-mcp is a hosted endpoint at https://mcp.oxylabs.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.oxylabs.io
claude mcp add --transport http io-oxylabs-oxylabs-mcp 'https://mcp.oxylabs.io/mcp'
What is the io.oxylabs/oxylabs-mcp server?
io.oxylabs/oxylabs-mcp is listed in the public MCP registry as io.oxylabs/oxylabs-mcp. Fetch and process content from specified URLs & sources using the Oxylabs Web Scraper API. This page covers its hosted endpoint (https://mcp.oxylabs.io/mcp).
Is the io.oxylabs/oxylabs-mcp server safe to use?
io.oxylabs/oxylabs-mcp scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.oxylabs/oxylabs-mcp server expose?
io.oxylabs/oxylabs-mcp exposes 10 tools: ai_crawler, ai_scraper, ai_browser_agent, ai_search, generate_schema, and 5 more. Their descriptions and schemas cost roughly 2,975 tokens of context every time the server is loaded.
Does the io.oxylabs/oxylabs-mcp server require authentication?
No. We connected to io.oxylabs/oxylabs-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.oxylabs/oxylabs-mcp server still maintained?
io.oxylabs/oxylabs-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.