io.github.NovadaLabs/proxy4agents-mcp
NPM · BESTPROXY4AGENTS-MCP · SCANNED AUG 3
Residential proxy MCP for AI agents — geo-targeting, sticky sessions, anti-bot bypass.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (189 of 190), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (189 of 190), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 111 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 866 tokens (~144/item across 6 items; 6 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · bestproxy4agents-mcp
claude mcp add novadalabs-proxy4agents-mcp -- npx -y bestproxy4agents-mcp
codex mcp add novadalabs-proxy4agents-mcp -- npx -y bestproxy4agents-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"novadalabs-proxy4agents-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"bestproxy4agents-mcp"
],
"enabled": true
}
}
} openclaw mcp add novadalabs-proxy4agents-mcp --command npx --arg -y --arg bestproxy4agents-mcp
mcp_servers:
novadalabs-proxy4agents-mcp:
command: "npx"
args: ["-y", "bestproxy4agents-mcp"] {
"mcpServers": {
"novadalabs-proxy4agents-mcp": {
"command": "npx",
"args": [
"-y",
"bestproxy4agents-mcp"
]
}
}
} 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.
- 3 Aug 26 +33
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Schema quality: unverified → good ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.27 ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 2 Aug 26 +13
- Dependency health: partial → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- 1 Aug 26 −13
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- 31 Jul 26 −9
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +21
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −21
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 39
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 189 packages
189 packages in the resolved dependency tree · 187 deprecated · 56 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
agentproxy_extract ~219
Extract structured data from any URL through a residential proxy. Fetches the page and extracts named fields (title, price, description, rating, author, date, image, links, headings, etc.) using meta tags, Open Graph, JSON-LD, and HTML patterns. Returns clean key-value output — no HTML parsing needed by the agent.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | — | City-level targeting (e.g. newyork, london, tokyo) |
| country | string | — | 2-letter country code for geo-targeting (e.g. US, DE, JP) |
| fields | array | yes | Field names to extract: title, price, currency, description, image, rating, review_count, author, date, url, links, headings, h2, or any JSON-LD/meta field name |
| session_id | string | — | Reuse same ID to keep the same IP across calls |
| timeout | number | — | Timeout in seconds (1-120) |
| url | string | yes | The URL to extract data from |
No output schema declared.
No examples provided.
agentproxy_fetch ~188
Fetch any URL through a residential proxy network (2M+ IPs, 195 countries, anti-bot bypass). Works on Amazon, LinkedIn, Cloudflare-protected pages, and most commercial sites. Use agentproxy_render instead for JavaScript-heavy pages that need a real browser.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | — | City-level targeting: newyork, london, tokyo, ... |
| country | string | — | 2-letter country code: US, DE, JP, GB, BR, ... (195+ options) |
| format | string | — | markdown strips HTML tags; raw returns full HTML |
| session_id | string | — | Use the same ID across calls to stay on the same IP (letters, numbers, underscores only — no hyphens) |
| timeout | number | — | Timeout in seconds (1-120) |
| url | string | yes | The URL to fetch |
No output schema declared.
No examples provided.
agentproxy_render ~142
[BETA] Render a JavaScript-heavy page using Novada's Browser API (real Chromium, full JS execution). Use this for SPAs, React/Vue apps, and sites that require JavaScript to load content. Requires NOVADA_BROWSER_WS env var. For static/HTML pages, agentproxy_fetch is faster.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | — | markdown strips tags; html returns full HTML; text strips tags + links |
| timeout | number | — | Timeout in seconds (5-120) |
| url | string | yes | The URL to render |
| wait_for | string | — | CSS selector to wait for before extracting (e.g. '.product-title') |
No output schema declared.
No examples provided.
agentproxy_search ~124
Structured web search via Novada (Google). Returns titles, URLs, and descriptions — no HTML parsing needed. Best for finding pages and factual queries. For reading a specific URL, use agentproxy_fetch instead.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | — | Country for localized results (e.g. us, uk, de) |
| engine | string | — | Search engine (google) |
| language | string | — | Language code (e.g. en, zh, de) |
| num | number | — | Number of results (1-20) |
| query | string | yes | The search query |
No output schema declared.
No examples provided.
agentproxy_session ~152
Fetch a URL with a sticky session — the same residential IP is used for every call with the same session_id. Use this for multi-step workflows where IP consistency matters: login flows, paginated scraping, price monitoring.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | — | City-level targeting (e.g. newyork, london, tokyo) |
| country | string | — | 2-letter country code |
| format | string | — | — |
| session_id | string | yes | Unique session ID — reuse the same value to keep the same IP (letters, numbers, underscores only — no hyphens) |
| timeout | number | — | Timeout in seconds (1-120) |
| url | string | yes | The URL to fetch |
No output schema declared.
No examples provided.
agentproxy_status ~41
Check proxy network health — live node count, device types, active provider, service status. Use before starting a large scraping workflow to confirm the network is healthy.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.