socks-proxy-agent 10.x

Use socks-proxy-agent ^10.0.0 to create SOCKS agents for Node HTTP clients and compatible integrations.

For

socks-proxy-agent@10.1.0

Verified

2026-09-08, 3 examples executed

Package

@modootoday/pmcp-socks-proxy-agent@10.0.0

What it covers

• Version and module requirements
• Constructing an agent
• Options
• Using the agent with Node HTTP clients
• Common migration mistake
• Not covered

One example from this skill

This is the skill's own text, not a summary of it. It runs: that is what verifying means here.

import assert from 'node:assert/strict';
import { SocksProxyAgent } from 'socks-proxy-agent';

const agent = new SocksProxyAgent(
  'socks://your-name%40example.com:secret@proxy.example.com:1080'
);

assert.deepEqual(SocksProxyAgent.protocols, [
  'socks',
  'socks4',
  'socks4a',
  'socks5',
  'socks5h',
]);
assert.equal(typeof agent.proxyUrl, 'string');
assert.equal(agent.proxyUrl, 'socks://your-name%40example.com:secret@proxy.example.com:1080');
assert.equal(typeof agent.shouldLookup, 'boolean');
assert.equal(typeof agent.proxy, 'object');

What it did in the sandbox

Verifying this skill meant installing the package and running code against it with no route out. Nothing was observed. The full ledger lists every package examined, including the ones that never became a skill.

Nothing observed is not a finding of safety. It means one run, under one policy, produced nothing to report.

Getting it

With a subscription:

npx -y @modootoday/pmcp login
npx -y @modootoday/pmcp install @modootoday/pmcp-socks-proxy-agent

It installs as a dev dependency of your project, and the MCP server finds it there like any other skill.