io.github.Goldentrii/proxy-veil
NPM · PROXY-VEIL
Residential proxy MCP server for AI agents — geo-targeting, sticky sessions, anti-bot bypass.
Available components
Last scanned (4 hours ago)
Scores higher than 43% of npm servers
Category Web Scraping
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 → Why this is hard to score →
Supply Chain Security90
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects basic-ftp 5.3.1, reached via puppeteer-core > @puppeteer/browsers > proxy-agent > pac-proxy-agent > get-uri > basic-ftp. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 57 of 188 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency13
- 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
- Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it. See how to fix → Fail
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 629 tokens (~125/item across 5 items; 5 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 Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 5 Nov 26 −3
- Stability: pass → 0.77 functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 · Analysed npm/proxy-veil@1.5.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 4 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-c475-qrg2-pj4r | CVE-2026-102990 | high | yes | |
| GHSA-7pqw-9j4j-h8q3 | CVE-2026-19693 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H | no |
| GHSA-jmr9-qjv8-65gv | CVE-2026-56876 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N | no |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 188 packages
| Packages resolved | 188 |
|---|---|
| Stale | 57 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
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 ~128
[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 | – | – |
| 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 ~148
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 |
| 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.
How do I install the io.github.Goldentrii/proxy-veil MCP server?
io.github.Goldentrii/proxy-veil runs locally as an npm package, launched with npx -y proxy-veil. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · proxy-veil
claude mcp add goldentrii-proxy-veil -- npx -y proxy-veil
What is the io.github.Goldentrii/proxy-veil MCP server?
io.github.Goldentrii/proxy-veil is an MCP server listed in the public MCP registry as io.github.Goldentrii/proxy-veil. Residential proxy MCP server for AI agents, geo-targeting, sticky sessions, anti-bot bypass. This page covers its npm package (proxy-veil).
Is the io.github.Goldentrii/proxy-veil MCP server safe to use?
io.github.Goldentrii/proxy-veil scores 72 out of 100 on VerifyMCP. We recorded 4 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. 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.github.Goldentrii/proxy-veil MCP server expose?
io.github.Goldentrii/proxy-veil exposes 5 tools: agentproxy_fetch, agentproxy_render, agentproxy_search, agentproxy_session, agentproxy_status. Their descriptions and schemas cost roughly 629 tokens of context every time the server is loaded.
Is the io.github.Goldentrii/proxy-veil MCP server still maintained?
io.github.Goldentrii/proxy-veil 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.
What licence is the io.github.Goldentrii/proxy-veil MCP server under?
io.github.Goldentrii/proxy-veil declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.