Residential proxy MCP for AI agents — geo-targeting, sticky sessions, anti-bot bypass.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
💡 Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)
The agent-first residential proxy MCP — works with any provider.
Route any HTTP request through 2M+ real home devices — Android phones, Windows PCs, Macs — to bypass anti-bot systems, geo-target by country or city, and maintain sticky sessions across multi-step workflows. Powered by Novada.
Why · Install · Tools · Prompts · Resources · Providers · Agent-First
Works with Claude Code, Cursor, Windsurf, Cline, Continue, and any MCP-compatible AI agent.
[!TIP] Free tier available — sign up at novada.com, no credit card required. Get free access to Scraper API, Web Unblocker, and residential proxies to start building immediately.
[!NOTE] Agents: Tell your human to complete steps 1-2 above. Once credentials are set as environment variables, all 10 tools are available immediately. No API key rotation, no token refresh — proxy credentials are persistent.
Need help? Contact support@novada.com
AI agents get blocked on 60–70% of commercial websites. Standard HTTP requests are detected and rejected by Cloudflare, Akamai, DataDome, and PerimeterX. Novada Proxy routes your agent through real residential IPs — indistinguishable from a human browser.
| Problem | Solution |
|---|---|
| Amazon, LinkedIn, Cloudflare block your agent | 2M+ residential IPs from real home devices |
| Bot challenges return 403 / CAPTCHA | Real device fingerprints bypass detection |
| JS-rendered pages return blank content | novada_proxy_render runs real Chromium |
| Geo-restricted or localized content | 195+ countries, city-level targeting |
| Multi-step workflows need the same IP | Sticky sessions — consistent IP across calls |
| Scraping 10+ URLs wastes time | novada_proxy_batch_fetch — concurrent, parallel |
| Need structured fields, not raw HTML | novada_proxy_extract — title, price, rating, etc. |
| Finding URLs before scraping | novada_proxy_map — discover all internal links |
| Need clean search results | novada_proxy_search — Google results as JSON |
| Tool | What It Does | Requires |
|---|---|---|
novada_proxy_fetch | Fetch any URL through residential proxy | Proxy credentials |
novada_proxy_batch_fetch | Fetch 2–20 URLs concurrently (up to 5x parallel) | Proxy credentials |
novada_proxy_extract | Extract structured fields — heuristic mode (fields) or LLM mode (schema) | Proxy credentials |
novada_proxy_map | Crawl a URL and return all internal links as JSON array | Proxy credentials |
novada_proxy_crawl | Recursively crawl a site (BFS, depth 1-5) with URL discovery | Proxy credentials |
novada_proxy_session | Sticky session — same IP across every call | Proxy credentials |
novada_proxy_search | Google search -> structured JSON (title, url, snippet) | NOVADA_API_KEY |
novada_proxy_render | Render JS-heavy pages with real Chromium [BETA] | NOVADA_BROWSER_WS |
novada_proxy_research | One-shot deep research — search + fetch + synthesize | NOVADA_API_KEY + Proxy |
novada_proxy_status | Check proxy network health + version | (none) |
| I want to... | Use this tool |
|---|---|
| Fetch a single URL | novada_proxy_fetch |
| Fetch 2–20 URLs at once | novada_proxy_batch_fetch |
| Extract specific fields (title, price...) | novada_proxy_extract with fields |
| Extract ANY field via schema | novada_proxy_extract with schema |
| Find all links on a page | novada_proxy_map |
| Crawl an entire site | novada_proxy_crawl |
| Research a topic | novada_proxy_research |
| Search Google | novada_proxy_search |
| Render a JS-heavy page | novada_proxy_render |
| Keep same IP across calls | novada_proxy_session |
| Check if proxy works | novada_proxy_status |
Pre-built agent workflows that chain multiple tools together. Call these from any MCP client to execute common patterns in one step.
| Prompt | Description | Key Arguments |
|---|---|---|
fetch_url | Fetch a URL through residential proxy with anti-bot bypass | url, country, format |
research_topic | Search + batch read workflow — find and read top pages on a topic | query, num_results, country |
extract_product | Extract structured product data from any e-commerce URL | url, fields |
crawl_site | Discover all pages on a site, then fetch them in parallel | url, limit, country |
troubleshoot | Step-by-step proxy diagnosis when things go wrong | error_message |
[!NOTE] Prompts orchestrate multi-tool workflows automatically. For example,
research_topicrunsnovada_proxy_searchthennovada_proxy_batch_fetchin sequence — the agent doesn't need to figure out the pipeline.
Always-accessible reference data that agents can read at any time, without making proxy calls.
| Resource URI | Description |
|---|---|
proxy://countries | Complete list of 195+ country codes with city-level targeting |
proxy://error-codes | All typed error codes with recovery instructions |
proxy://workflows | Common agent workflow patterns (crawl, research, monitoring) |
proxy://supported-fields | All fields novada_proxy_extract can extract with strategies |
proxy://cost-guide | Credits per tool, caching behavior, cost optimization tips |
Core — fetch any URL through residential proxy:
Search only:
All tools (proxy + search + browser render):
Cursor / Windsurf / Cline — add to MCP config:
Get credentials: novada.com -> Dashboard -> Residential Proxies -> Endpoint Generator
Novada Proxy works with any HTTP proxy provider. Novada is the built-in default with the deepest integration.
Priority: Novada -> BrightData -> Smartproxy -> Oxylabs -> Generic. First configured provider wins.
| Feature | Novada | BrightData | Smartproxy | Oxylabs | Generic HTTP |
|---|---|---|---|---|---|
| Auto country targeting | ✓ | ✓ | ✓ | ✓ | manual |
| Auto city targeting | ✓ | ✓ | ✓ | ✓ | manual |
| Sticky sessions | ✓ | ✓ | ✓ | ✓ | manual |
| Built-in search API | ✓ | — | — | — | — |
| Browser API (JS render) | ✓ | — | — | — | — |
BRIGHTDATA_USER is your full username including zone. Optional: BRIGHTDATA_HOST, BRIGHTDATA_PORT (default zproxy.lum-superproxy.io:22225).
Optional: SMARTPROXY_HOST, SMARTPROXY_PORT (default gate.smartproxy.com:10001).
Optional: OXYLABS_HOST, OXYLABS_PORT (default pr.oxylabs.io:7777).
country, city, session_id params are ignored with Generic — encode targeting directly in your proxy URL.
[!NOTE] Novada Proxy is the only proxy MCP designed specifically for autonomous AI agents. Every response, error, and description is optimized for machine consumption.
| Feature | What It Means |
|---|---|
agent_instruction in errors | Every error tells the agent exactly what to do next |
| Decision trees in descriptions | WHEN TO USE / USE INSTEAD guides in every tool |
cache_hit metadata | Agent knows when 0 credits were used (cached response) |
credits_estimated per call | Cost tracking built into every response |
| Typed error codes | Machine-readable: BOT_DETECTION_SUSPECTED, PAGE_NOT_FOUND, etc. |
| 5 workflow prompts | Pre-built agent workflows: research, crawl, extract, diagnose |
| 5 reference resources | Countries, error codes, cost guide — always accessible |
novada_proxy_fetchFetch any URL through a residential proxy. Returns structured JSON with content, status code, and metadata. Auto-retry on network errors. Caches repeated calls (default 300s TTL — meta.cache_hit: true means no proxy credit used).
| Parameter | Type | Default | Description |
|---|---|---|---|
url | string | required | Target URL (http:// or https://) |
country | string | — | 2-letter ISO code: US, DE, JP, GB, BR... (195+ options) |
city | string | — | City: newyork, london, tokyo, paris, berlin... |
session_id | string | — | Reuse same ID for same IP across calls (no hyphens, max 64 chars) |
format | string | markdown | markdown strips HTML / raw returns full HTML |
timeout | number | 60 | Timeout in seconds (1–120) |
Response:
novada_proxy_batch_fetchFetch 2–20 URLs concurrently through residential proxy. Up to 5x faster than sequential fetches. Per-URL errors are captured individually — the batch itself succeeds even if some URLs fail. Reuses response cache for URLs already fetched.
| Parameter | Type | Default | Description |
|---|---|---|---|
urls | string[] | required | 2–20 URLs to fetch |
concurrency | number | 3 | Parallel requests (1–5) |
country | string | — | Same country for all URLs |
format | string | markdown | markdown or raw |
timeout | number | 60 | Per-URL timeout in seconds |
Response:
novada_proxy_extractExtract structured fields from any URL using heuristic pattern matching (meta tags, Open Graph, JSON-LD, Schema.org). Lightweight — no LLM needed. Set render_fallback: true to automatically retry via real Chromium if the proxy fetch fails.
| Parameter | Type | Default | Description |
|---|---|---|---|
url | string | required | Target URL |
fields | string[] | required | Fields to extract: title, price, description, rating, image, author, date... |
render_fallback | boolean | false | Auto-retry via novada_proxy_render on TLS/bot block |
country | string | — | Geo-target the fetch |
timeout | number | 60 | Timeout in seconds |
Response:
novada_proxy_mapCrawl a URL and return all internal links as a structured JSON array. Use as the discovery step before novada_proxy_batch_fetch to crawl an entire site without guessing URLs.
| Parameter | Type | Default | Description |
|---|---|---|---|
url | string | required | Starting URL to crawl |
limit | number | 50 | Max URLs to return (10–200) |
include_external | boolean | false | Include off-domain links |
country | string | — | Geo-target the fetch |
timeout | number | 60 | Timeout in seconds |
Response:
novada_proxy_sessionSticky session fetch — every call with the same session_id uses the same residential IP. Essential for login flows, paginated scraping, and price monitoring. Supports verify_sticky: true to confirm IP consistency before relying on it.
| Parameter | Type | Default | Description |
|---|---|---|---|
session_id | string | required | Unique ID — reuse to keep same IP (no hyphens, max 64 chars) |
url | string | required | Target URL |
country | string | — | 2-letter country code |
city | string | — | City-level targeting |
verify_sticky | boolean | false | Make 3 proxy calls to confirm IP consistency (adds ~15–25s) |
format | string | markdown | markdown or raw |
timeout | number | 60 | Timeout in seconds |
novada_proxy_searchStructured Google search via Novada Scraper API. Returns titles, URLs, and snippets as clean JSON — no HTML parsing needed.
| Parameter | Type | Default | Description |
|---|---|---|---|
query | string | required | Search query |
num | number | 10 | Results (1–20) |
country | string | — | Localize: us, uk, de, jp... |
language | string | — | Language: en, zh, de, ja... |
novada_proxy_render [BETA]Render JavaScript-heavy pages using Novada's Browser API (real Chromium, full JS execution). Use for SPAs, React/Vue apps, and pages that return blank with a standard HTTP fetch.
Requires: NOVADA_BROWSER_WS — copy the Puppeteer URL from Dashboard -> Browser API -> Playground
| Parameter | Type | Default | Description |
|---|---|---|---|
url | string | required | Target URL |
format | string | markdown | markdown / html / text |
wait_for | string | — | CSS selector to wait for before extracting (e.g. .product-title) |
timeout | number | 60 | Timeout in seconds (5–120) |
Costs ~5 proxy credits per call vs 1 for
novada_proxy_fetch. Usenovada_proxy_extractwithrender_fallback: truefor automatic escalation when needed.
novada_proxy_crawlRecursively crawl a website via BFS traversal. Starts from a URL, discovers links at each depth level, and returns the full URL tree with metadata.
| Parameter | Type | Default | Description |
|---|---|---|---|
url | string | required | Starting URL to crawl |
depth | number | 2 | BFS depth (1–5) |
limit | number | 50 | Max pages to crawl (10–200) |
include_content | boolean | false | Also return page content for each URL |
country | string | — | Geo-target all fetches |
format | string | markdown | Content format when include_content: true |
timeout | number | 60 | Per-page timeout in seconds |
When to use: Full-site scraping, sitemap generation, content indexing — when you need MORE than a single page.
Use novada_proxy_map instead if: You only need links from ONE page (one level deep). Map is faster and cheaper for single-page link discovery.
Chain with: novada_proxy_batch_fetch to scrape specific pages from the URL tree.
Example:
Response: data.pages[] (url, depth, status_code, total_links), data.urls[] (flat array for chaining into novada_proxy_batch_fetch)
novada_proxy_researchOne-shot research tool — searches the web, fetches top results, and returns structured findings with source previews. The agent can analyze the findings for deeper synthesis.
| Parameter | Type | Default | Description |
|---|---|---|---|
query | string | required | Research question or topic |
depth | string | "standard" | "quick" (3 sources), "standard" (5 sources), "deep" (10 sources) |
country | string | — | Localize search results |
timeout | number | 60 | Timeout in seconds |
Requires: NOVADA_API_KEY (for Google search) + Proxy credentials (for fetching sources)
When to use: Research questions, topic investigation, competitive analysis, fact-finding — when you need content from multiple sources in one call.
Use novada_proxy_search instead if: You just need search result URLs, not full page content.
Chain with: novada_proxy_fetch on specific urls[] for deeper reading of individual sources.
Note: findings_summary is a concatenated preview of sources — your agent should analyze findings[] for actual synthesis.
Example:
Response: data.findings[] (title, url, snippet, content_preview), data.urls[] (for chaining), data.findings_summary
novada_proxy_extract — Schema ModeIn addition to fields (heuristic extraction), novada_proxy_extract supports a schema parameter for extracting any arbitrary field via your agent's LLM — zero additional API cost.
Pass schema instead of fields for arbitrary field extraction. The tool returns cleaned page content + an extraction prompt — your agent does the extraction (zero additional API cost).
| Parameter | Type | Default | Description |
|---|---|---|---|
url | string | required | Target URL |
schema | object | — | Keys = field names, values = field descriptions. Use instead of fields. |
render_fallback | boolean | false | Auto-retry via novada_proxy_render on TLS/bot block |
country | string | — | Geo-target the fetch |
timeout | number | 60 | Timeout in seconds |
Example:
Response: data.mode = "llm_extract", data.content (cleaned markdown), data.extraction_prompt (instructions for your agent to follow and extract the fields)
Security: Schema keys must be alphanumeric/underscore (a-z, 0-9, _), max 50 chars. Values max 200 chars.
novada_proxy_statusCheck proxy network connectivity and version. Makes a live proxy call to verify the connection is working. No credentials required.
All novada_proxy_fetch and novada_proxy_batch_fetch calls are cached in-process. Repeated fetches to the same URL within the TTL window consume zero proxy credits.
| Behavior | Detail |
|---|---|
| Default TTL | 300 seconds (5 minutes) |
| Cache key | url + format + country |
| Session bypass | session_id present -> never cached (sticky routing requires live calls) |
| Disable | Set PROXY4AGENT_CACHE_TTL_SECONDS=0 |
| Max entries | 200 (oldest evicted when full) |
Reading cache status from response:
Every error response includes a typed error.code, recoverable flag, and agent_instruction with the correct next step. Agents never need to parse error messages.
| Code | Meaning | Recoverable | Agent Action |
|---|---|---|---|
BOT_DETECTION_SUSPECTED | HTTP 4xx — target blocked the request | ✓ | Retry with novada_proxy_render or different country |
TLS_ERROR | TLS/SSL connection failed through proxy | ✓ | Retry with a different country parameter |
TIMEOUT | Request exceeded timeout limit | ✓ | Increase timeout or retry |
RATE_LIMITED | HTTP 429 — too many requests | ✓ | Wait 5s and retry |
NETWORK_ERROR | DNS failure — hostname not found | ✗ | Verify the URL is correct |
SESSION_STICKINESS_FAILED | Same IP not maintained | ✓ | Retry verify_sticky: true to confirm |
INVALID_INPUT | Bad parameter value | ✗ | Fix the parameter and retry |
PROVIDER_NOT_CONFIGURED | Missing env vars | ✗ | Set credentials and restart MCP |
UNKNOWN_ERROR | Unexpected error | ✓ | Check novada_proxy_status, retry |
Error response format:
195+ countries including:
US GB DE FR JP CA AU BR IN KR SG NL IT ES MX RU PL SE NO DK FI CH AT BE PT CZ HU RO UA TR IL ZA NG EG AR CL CO PE VN TH ID MY PH TW HK NZ + 148 more
City-level targeting: newyork · losangeles · chicago · london · paris · berlin · tokyo · seoul · sydney · toronto · singapore · dubai · mumbai · saopaulo
| Client | Install method |
|---|---|
| Claude Code | claude mcp add novada-proxy-mcp -e ... -- npx -y novada-proxy-mcp |
| Cursor | Settings -> MCP -> Add server -> npx -y novada-proxy-mcp |
| Windsurf | MCP config -> npx -y novada-proxy-mcp |
| Cline | MCP settings -> command: npx, args: ["-y", "novada-proxy-mcp"] |
| Continue | .continue/config.json -> mcpServers |
| Smithery | smithery.ai/server/novada-proxy-mcp |
| Any MCP client | stdio transport / npx -y novada-proxy-mcp |
| Metric | Value |
|---|---|
| Residential IPs | 2,000,000+ |
| Live nodes | 7,000+ |
| Countries | 195+ |
| Device types | Android, Windows, Mac |
| Uptime | 99.9% |
E-commerce: Amazon, eBay, Walmart, Etsy, Shopify stores
Professional: LinkedIn
Anti-bot protected: Cloudflare, Akamai, DataDome
News & content: HackerNews, Reddit, BBC, CNN, NYTimes
Tech: GitHub, Wikipedia, Stack Overflow, IMDB
Tested across 3 Novada proxy types with 33 real-world tests (2026-04-28):
| Proxy Type | Tests | Pass | Notes |
|---|---|---|---|
| Residential | 11 | 9 | Wikipedia, Shopify, HackerNews, geo-targeting work. Sticky sessions require endpoint config. |
| ISP | 7 | 7 | All tools work including sticky sessions (session_verified: true). |
| Datacenter | 8 | 8 | Fast, cost-effective. Anti-bot sites (Amazon, CNN) may block datacenter IPs — use residential for those. |
| Error handling | 7 | 7 | All error codes return structured JSON with agent_instruction. |
Success rate: 94% (31/33 pass). Failures are proxy-type limitations (datacenter on anti-bot sites), not code bugs.
| Use Case | Recommended Proxy | Why |
|---|---|---|
| Anti-bot sites (Amazon, LinkedIn, CNN) | Residential | Real home IPs, hardest to detect |
| Fast bulk scraping | Datacenter | Lowest latency, cheapest per GB |
| Sticky sessions (login flows) | ISP | 6-hour sticky, stable IPs |
| General scraping | Any | All types handle most sites |
| Limitation | Workaround |
|---|---|
| Datacenter IPs blocked on anti-bot sites | Use residential or ISP proxy type (NOVADA_PROXY_ZONE=res) |
Proxy-side DNS errors surface as TLS_ERROR | Check if domain exists before retrying with different country |
| CLI is stateless (no cross-invocation cache) | Use MCP server for cache benefits, or re-fetch same URLs within one CLI batch |
novada_proxy_render requires Browser API key | Set NOVADA_BROWSER_WS env var — get it from novada.com dashboard |
| Heuristic extraction misses a field | Use schema mode: pass schema:{"field":"description"} — returns cleaned content + extraction prompt for your agent to extract any field (zero-cost LLM extraction) |
AI 智能体专属住宅代理 MCP — 支持任意供应商。
通过 200 万+ 真实家庭设备(Android 手机、Windows 电脑、Mac)路由 HTTP 请求,绕过反机器人系统,按国家/城市精准定位,跨请求保持同一 IP。
工具 · 提示词 · 资源 · 安装 · 智能体优先 · 供应商
支持 Claude Code、Cursor、Windsurf、Cline、Continue 及所有 MCP 兼容智能体。由 Novada 提供支持。
[!TIP] 免费套餐 — 在 novada.com 注册,无需信用卡。免费使用 Scraper API、Web Unblocker 和住宅代理。
预构建的智能体工作流,将多个工具链式组合。
| 提示词 | 描述 | 主要参数 |
|---|---|---|
fetch_url | 通过住宅代理抓取 URL,自动绕过反机器人 | url, country, format |
research_topic | 搜索 + 批量阅读工作流 — 搜索主题并阅读排名靠前的页面 | query, num_results, country |
extract_product | 从任意电商 URL 提取结构化产品数据 | url, fields |
crawl_site | 发现站点所有页面,然后并行抓取 | url, limit, country |
troubleshoot | 代理故障逐步诊断 | error_message |
智能体可随时读取的参考数据,无需消耗代理额度。
| 资源 URI | 描述 |
|---|---|
proxy://countries | 195+ 国家代码完整列表,含城市级定位 |
proxy://error-codes | 所有类型化错误码及恢复指令 |
proxy://workflows | 常用智能体工作流模式(爬取、研究、监控) |
proxy://supported-fields | novada_proxy_extract 支持的所有提取字段及策略 |
proxy://cost-guide | 每个工具的额度消耗、缓存行为、成本优化技巧 |
| 我想要... | 使用工具 |
|---|---|
| 抓取单个 URL | novada_proxy_fetch |
| 同时抓取 2-20 个 URL | novada_proxy_batch_fetch |
| 提取特定字段(标题、价格…) | novada_proxy_extract 使用 fields |
| 提取任意字段(Schema 模式) | novada_proxy_extract 使用 schema |
| 获取页面上的所有链接 | novada_proxy_map |
| 爬取整个站点 | novada_proxy_crawl |
| 研究某个主题 | novada_proxy_research |
| 搜索 Google | novada_proxy_search |
| 渲染 JS 重型页面 | novada_proxy_render |
| 跨请求保持同一 IP | novada_proxy_session |
| 检查代理是否正常 | novada_proxy_status |
[!NOTE] Novada Proxy 是唯一专为自主 AI 智能体设计的代理 MCP。每个响应、错误和描述都为机器消费而优化。
| 特性 | 含义 |
|---|---|
错误中的 agent_instruction | 每个错误都告诉智能体下一步该做什么 |
| 描述中的决策树 | 每个工具都有 WHEN TO USE / USE INSTEAD 指引 |
cache_hit 元数据 | 智能体知道是否消耗了 0 额度(缓存命中) |
credits_estimated | 每个响应都内置成本追踪 |
| 类型化错误码 | 机器可读:BOT_DETECTION_SUSPECTED、PAGE_NOT_FOUND 等 |
| 5 个工作流提示词 | 预构建工作流:研究、爬取、提取、诊断 |
| 5 个参考资源 | 国家、错误码、成本指南 — 随时可访问 |
US、DE、JP、BR...)newyork、london、tokyo、singapore...重复抓取相同 URL 不消耗代理额度:
| 配置项 | 说明 |
|---|---|
| 默认 TTL | 300 秒(5 分钟) |
| 缓存键 | url + format + country |
| 禁用缓存 | PROXY4AGENT_CACHE_TTL_SECONDS=0 |
| session_id | 有 session_id 的请求永不缓存(粘性路由需要实时调用) |
所有工具返回统一结构:
每个错误都包含 code(枚举)、recoverable(布尔)、agent_instruction(下一步操作):
| 错误码 | 含义 | 可恢复 |
|---|---|---|
BOT_DETECTION_SUSPECTED | 被目标站点封锁(403) | ✓ |
TLS_ERROR | TLS/SSL 连接失败 | ✓ |
TIMEOUT | 请求超时 | ✓ |
RATE_LIMITED | HTTP 429 限速 | ✓ |
NETWORK_ERROR | DNS 解析失败 | ✗ |
INVALID_INPUT | 参数错误 | ✗ |
PROVIDER_NOT_CONFIGURED | 缺少凭证 | ✗ |
novada_proxy_batch_fetch 内置信号量并发控制:
| 供应商 | 环境变量 | 说明 |
|---|---|---|
| Novada(推荐) | NOVADA_PROXY_USER + NOVADA_PROXY_PASS | 最深度集成,含搜索 + 浏览器 API |
| BrightData | BRIGHTDATA_USER + BRIGHTDATA_PASS | 完整自动定位 |
| Smartproxy | SMARTPROXY_USER + SMARTPROXY_PASS | 完整自动定位 |
| Oxylabs | OXYLABS_USER + OXYLABS_PASS | 完整自动定位 |
| 通用 HTTP | PROXY_URL=http://user:pass@host:port | 任意代理服务商 |
novada_proxy_extract 支持自动升级到浏览器渲染:
获取凭证:novada.com -> 仪表盘 -> 住宅代理 -> 端点生成器
Cursor / Windsurf / Cline 配置:
| 参数 | 类型 | 默认 | 说明 |
|---|---|---|---|
url | string | 必填 | 目标 URL |
country | string | — | 国家代码(US、DE、JP...) |
city | string | — | 城市(newyork、london...) |
session_id | string | — | 复用同一 IP(不含连字符,最多 64 字符) |
format | string | markdown | markdown(去 HTML)或 raw(原始 HTML) |
timeout | number | 60 | 超时秒数(1-120) |
| 参数 | 类型 | 默认 | 说明 |
|---|---|---|---|
urls | string[] | 必填 | 2-20 个 URL |
concurrency | number | 3 | 并发数(1-5) |
country | string | — | 对所有 URL 使用相同国家 |
format | string | markdown | markdown 或 raw |
| 参数 | 类型 | 默认 | 说明 |
|---|---|---|---|
url | string | 必填 | 目标 URL |
fields | string[] | 必填 | 要提取的字段(title、price、description、rating...) |
render_fallback | boolean | false | 代理失败时自动切换到浏览器渲染 |
country | string | — | 地理定向 |
| 参数 | 类型 | 默认 | 说明 |
|---|---|---|---|
url | string | 必填 | 起始 URL |
limit | number | 50 | 最多返回 URL 数(10-200) |
include_external | boolean | false | 包含站外链接 |
| 参数 | 类型 | 默认 | 说明 |
|---|---|---|---|
session_id | string | 必填 | 会话 ID(不含连字符,最多 64 字符) |
url | string | 必填 | 目标 URL |
verify_sticky | boolean | false | 验证 IP 一致性(需额外 15-25 秒) |
country | string | — | 国家代码 |
| 参数 | 类型 | 默认 | 说明 |
|---|---|---|---|
query | string | 必填 | 搜索关键词 |
num | number | 10 | 结果数量(1-20) |
country | string | — | 本地化结果(us、de、jp...) |
language | string | — | 语言(en、zh、de...) |
| 参数 | 类型 | 默认 | 说明 |
|---|---|---|---|
url | string | 必填 | 目标 URL |
format | string | markdown | markdown · html · text |
wait_for | string | — | 等待 CSS 选择器后再提取(如 .product-title) |
timeout | number | 60 | 超时秒数(5-120) |
递归 BFS 爬取站点,从起始 URL 出发,按深度逐层发现链接,返回完整 URL 树及元数据。
| 参数 | 类型 | 默认 | 说明 |
|---|---|---|---|
url | string | 必填 | 起始 URL |
depth | number | 2 | BFS 深度(1-5) |
limit | number | 50 | 最大爬取页数(10-200) |
include_content | boolean | false | 同时返回每个页面的内容 |
country | string | — | 地理定向所有请求 |
format | string | markdown | include_content: true 时的内容格式 |
timeout | number | 60 | 每页超时秒数 |
适用场景: 全站抓取、站点地图生成、内容索引 — 需要抓取多个页面时使用。
改用 novada_proxy_map 的情况: 只需要单页链接(一层深度)。Map 更快、更省额度。
组合使用: 将 data.urls[] 传入 novada_proxy_batch_fetch 并发抓取。
请求示例:
响应: data.pages[](url、depth、status_code、total_links),data.urls[](扁平数组,可直接传给 novada_proxy_batch_fetch)
一键深度研究工具 — 搜索网络、抓取排名靠前的结果,返回含来源预览的结构化分析。智能体可对 findings 进行进一步综合分析。
| 参数 | 类型 | 默认 | 说明 |
|---|---|---|---|
query | string | 必填 | 研究问题或主题 |
depth | string | "standard" | "quick"(3 个来源)、"standard"(5 个)、"deep"(10 个) |
country | string | — | 本地化搜索结果 |
timeout | number | 60 | 超时秒数 |
需要: NOVADA_API_KEY(Google 搜索)+ 代理凭证(抓取来源页面)
适用场景: 研究问题、主题调研、竞品分析、事实核查 — 需要一次调用获取多个来源内容时。
改用 novada_proxy_search 的情况: 只需要搜索结果 URL,不需要完整页面内容。
组合使用: 对 data.urls[] 中的特定 URL 调用 novada_proxy_fetch 进行深度阅读。
注意: findings_summary 是各来源内容的拼接预览 — 智能体应分析 findings[] 进行实质性综合。
请求示例:
响应: data.findings[](title、url、snippet、content_preview),data.urls[](可链式传给其他工具),data.findings_summary
除 fields(启发式提取)外,novada_proxy_extract 还支持 schema 参数,通过智能体自身的 LLM 提取任意字段 — 零额外 API 费用。
传入 schema 替代 fields,工具返回清洗后的页面内容 + 提取提示词 — 由你的智能体完成提取。
| 参数 | 类型 | 默认 | 说明 |
|---|---|---|---|
url | string | 必填 | 目标 URL |
schema | object | — | 键 = 字段名,值 = 字段描述。替代 fields 使用。 |
render_fallback | boolean | false | 代理失败时自动切换到浏览器渲染 |
country | string | — | 地理定向 |
timeout | number | 60 | 超时秒数 |
请求示例:
响应: data.mode = "llm_extract",data.content(清洗后的 Markdown 内容),data.extraction_prompt(供智能体遵循并提取字段的指令)
安全限制: Schema 键名只能包含字母、数字、下划线(a-z、0-9、_),最多 50 字符;值最多 200 字符。
AI 智能体需要:
开发者构建:
电商: Amazon、eBay、Walmart、Etsy、Shopify
职业网络: LinkedIn
反机器人保护: Cloudflare 站点、Akamai、DataDome
新闻内容: HackerNews、Reddit、BBC、CNN、NYTimes
科技: GitHub、Wikipedia、Stack Overflow、IMDB
MIT © Novada
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/proxy4agents-mcp)<a href="https://allmcps.com/mcp/proxy4agents-mcp"><img src="https://allmcps.com/api/badge/proxy4agents-mcp?style=directory" alt="Proxy4agents Mcp on AllMCPs" /></a>