Other · Local MCP server
Proxy Veil
Residential proxy MCP server for AI agents - geo-targeting, sticky sessions, anti-bot bypass.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Goldentrii/proxy-veil- Version
- 1.5.4
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-04-09
- Updated
- 2026-04-09
- Publisher
- Goldentrii (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Goldentrii) · how
- Repository
- github.com/Goldentrii/proxy-veil
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | proxy-veil | 1.5.4 | stdio |
How to connect Proxy Veil
Proxy Veil runs locally from a Node.js package published to the npm registry: proxy-veil version 1.5.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y proxy-veil@1.5.4. It reads these environment variables: NOVADA_PROXY_USER (secret), NOVADA_PROXY_PASS (secret), NOVADA_API_KEY (secret), BRIGHTDATA_USER (secret), BRIGHTDATA_PASS (secret), SMARTPROXY_USER (secret), SMARTPROXY_PASS (secret), OXYLABS_USER (secret), OXYLABS_PASS (secret) and PROXY_URL (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"proxy-veil": {
"command": "npx",
"args": [
"-y",
"proxy-veil@1.5.4"
],
"env": {
"NOVADA_PROXY_USER": "<secret>",
"NOVADA_PROXY_PASS": "<secret>",
"NOVADA_API_KEY": "<secret>",
"BRIGHTDATA_USER": "<secret>",
"BRIGHTDATA_PASS": "<secret>",
"SMARTPROXY_USER": "<secret>",
"SMARTPROXY_PASS": "<secret>",
"OXYLABS_USER": "<secret>",
"OXYLABS_PASS": "<secret>",
"PROXY_URL": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from Goldentrii (GitHub)
| Server | Runs |
|---|---|
| Agent RecallCorrection-first agent memory. Precision KPI tracks if agents heed warnings. 5 layers, local-only. | Local · stdio |
More other servers
| Server | Runs |
|---|---|
| Proximo - the Proxmox MCP you can hand the keysThe Proxmox MCP you can hand the keys: VE/PBS/PMG/PDM. Plan, prove, undo, diagnose. MCP/A2A/API. | Local · stdio |
| Proxmox VEManage Proxmox VE nodes, VMs, containers, storage and snapshots. Read-only by default. | Local · stdio |
| ProxmoxMCP-PlusProxmox VE MCP server for VMs, LXCs, snapshots, backups, storage, and cluster operations. | Local · stdio |
| Proxy AIopsGoverned Traefik + Caddy + HAProxy ops: routes, upstreams, certs, 5xx RCA. 28 tools. | Local · stdio |
| Proxy4agents MCPResidential proxy MCP for AI agents - geo-targeting, sticky sessions, anti-bot bypass. | Local · stdio |
| ProxyclawResidential proxy MCP server. 175M+ IPs in 195+ countries with anti-bot bypass. | Local · stdio |
| ProxyCoveBuy and manage residential, mobile and datacenter proxies in 170+ countries, prepaid per GB. | Remote · HTTPLive check: ✓ handshake |
| ProxykeyIssue, rotate and revoke scoped API-key passes for 25+ providers - the agent never sees a real key. | Remote · HTTPLive check: sign-in required |